Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Overview

Collection communication involves both messaging and data transmission. The messaging part is illustrate below

The details on alams are described under Alarm communication. File list, checksums and salts, follows the same patter as for Get Communications. The "get" message is only sent to one pillar.

The data trasmission involved is described under Data transmission protocol. It can be used either in transmission of message parameters or data as a result of a request.

Sequence diagrams

Ckecksums

The sequence diagram for checksums corresponds to last part of a get operattion. The sequence diagram is given below. 

Checksum messages

The getChecksums message contains the same information as a get, except that it also must include:

  • Checksums algorithm for checksums

In case we want to open possibility to give resulting checksums in a respons message then the following parameter must be included

  • Optionally max count of checksums in reply message

Furthermore we will need a getChecksumsReplyData message.

Checksum data to be transmitted

The data must as minimum include:

  • Number of checksums included
  • Repeatedly for each file:
    • the file id
    • the file checksum
    • the time when the checksum was calculated (especially for off-line medias, there can be long inteervals between calculations, - in such cases this information is crucial for alarming)

File list

The sequence diagram for file list corresponds to last part of a get operattion. The sequence diagram is given below.

File list messages

The getFileList message contains the same information as a get.

In case we want to open possibility to give resulting file list in a respons message then the following parameter must be included

  • Optionally max count of files in reply message

Furthermore we will need a getFileListReplyData message.

File list data to be transmitted

The data must as minimum include:

  • Number of files included
  • Repeatedly for each file:
    • the file id
    • the time when the file was last seen (especially for off-line medias, there can be long inteervals between calculations, - in such cases this information is crucial for alarming)

Salts

The sequence diagram for salts corresponds to last part of a get operattion. The sequence diagram is given below.

Salt messages

The getSalts message contains the same information as a get, except that it also must include:

  • Checksums algorithm for checksum
  • Salt algorithm
  • Extra character to be included in calculation

In case we want to open possibility to give resulting checksums in a respons message then the following parameter must be included

  • Optionally max count of checksums in reply message

Furthermore we will need a getSaltsReplyData message.

Salt data to be transmitted

The data must as minimum include:

  • Number of checksums/salts included
  • Repeatedly for each file:
    • the file id
    • extra character included in calculation
    • the file checksum (from salt)
    • the time when the checksum was calculated (consistency with the rest)
  • No labels