We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
One of the attributes of PUT operations is the ability to specific a Synchronization type, i.e. one of WRITETHROUGH, WRITEBACK, or FLUSH.
Should the Operation sub-message of a P2POperation also include that ability?
If not, what is the expected (default) behavior for a PUT operation generated from a P2POperation? Is it it WRITETHROUGH, WRITEBACK, or FLUSH?
-Eric
The text was updated successfully, but these errors were encountered:
No branches or pull requests
One of the attributes of PUT operations is the ability to specific a Synchronization type, i.e. one of WRITETHROUGH, WRITEBACK, or FLUSH.
Should the Operation sub-message of a P2POperation also include that ability?
If not, what is the expected (default) behavior for a PUT operation generated from a P2POperation? Is it it WRITETHROUGH, WRITEBACK, or FLUSH?
-Eric
The text was updated successfully, but these errors were encountered: