Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Ckecksums

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

Checksum messages

...

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 checksummer checksums in svarbeskedreply message

Furthermore we will need a getChecksumsReplyData message.

...

  • 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 lists

Evt. max antal filer i svarbesked

Specifikt for checksummer skal denne information indeholde:

  • antal filer
  • information per fil (evt. repeterbar)
    • fil id
    • tidspunkt hvor filen sidst blev set (hvis det ikke er online, kan denne information være vigtig for alarmering)

Salts

Evt. ekstra tegn til direkte checksumscheck (Rosenthal NONCE)

Evt. max antal checksummer i svarbesked

Minimums informationer i request beskeder:

Specifikt for checksummer skal denne information indeholde:

  • antal filer
  • information per fil (evt. repeterbar)
    • fil id
    • salt algoritme
    • ekstra tegn i beregnin
    • tidspunkt hvor salt blev beregnet

File list

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

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. Image Added

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)