Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
petersilva opened this issue Mar 31, 2019 · 2 comments

Comments

@petersilva
Copy link
Contributor

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.

@petersilva 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
@petersilva
Copy link
Contributor Author

ownership is a missing field in the Sarracenia implementation which may be implemented in the near future.

@petersilva
Copy link
Contributor Author

MetPX/sarracenia#177

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant