You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Sarracenia, there is a use case involving pure directory mirroring. It means replicating a bit more file meta data. the wmo_mesh demonstration currently ignores these fields, and it is likely unnecessary for wmo usage. Documenting these fields as a demonstation that specific implementations may include fields that the general standard does not support, but both ends may use, but the intervening nodes should pass them unaltered.
The fields used to this:
mtime - unix/linux modification time.
atime - unix/linux access time
mode - unix/linux traditional octal permission bits
The data replication works fine without any of these fields, but some end points may want to interpret them.
The text was updated successfully, but these errors were encountered:
petersilva
changed the title
Mirrorring use case fields (why pass through headers one doesn't understand.)
Mirroring use case fields (why pass through headers one doesn't understand.)
Mar 31, 2019
In Sarracenia, there is a use case involving pure directory mirroring. It means replicating a bit more file meta data. the wmo_mesh demonstration currently ignores these fields, and it is likely unnecessary for wmo usage. Documenting these fields as a demonstation that specific implementations may include fields that the general standard does not support, but both ends may use, but the intervening nodes should pass them unaltered.
The fields used to this:
mtime - unix/linux modification time.
atime - unix/linux access time
mode - unix/linux traditional octal permission bits
The data replication works fine without any of these fields, but some end points may want to interpret them.
The text was updated successfully, but these errors were encountered: