Skip to content

Mirroring use case fields (why pass through headers one doesn't understand.) #11

@petersilva

Description

@petersilva

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions