-
Notifications
You must be signed in to change notification settings - Fork 187
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
changes should use a channel to update files atomically #1402
Comments
I don't see a big benefit from the change. From my point of view, it's a different way to do the same thing, which is serializing all the reads and writes. Using RLock and RUnlock should perform better since read requests won't block unless there is a write request (Lock/Unlock) ongoing. This allows reading data from multiple requests in parallel and without blocking eachother. Basically, reads should use RLock/RUnlock while writes should use Lock/Unlock. |
@butonic this is an old issue that was transferred from the archived |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
to get rid of the mutex we should use a channel to queue writes and reads to the data.
see owncloud/ocis-accounts#82 and owncloud/ocis-accounts#72
The text was updated successfully, but these errors were encountered: