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

Atomicity on edits #232

Open
LloydW93 opened this issue Nov 23, 2014 · 0 comments
Open

Atomicity on edits #232

LloydW93 opened this issue Nov 23, 2014 · 0 comments
Labels

Comments

@LloydW93
Copy link
Member

Currently, the documented advice for calling updateCacheObject is it should be done on every set.

This means that during an action that calls multiple sets, there are multiple writes to APC and an inconsistent state made available to other requests.

This should change to marking that a change to the object has been made, to be committed at the end of request processing.

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

No branches or pull requests

1 participant