Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
COLI-1216: Combinator: File is being used by another process #23
COLI-1216: Combinator: File is being used by another process #23
Changes from all commits
e9cbdaa
0c7cdcb
34d2386
0887b18
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Functionally, this is the same as a simple
lock
. However, aMutex
is a heavy way of synchronization across processed, what you don't need. This can either be a simple semaphore as I mentioned (with any number of readers and a single writer) or you can do a slightly more sophisticated way with a named locking approach, so the locks are different per resource bundle.Please decide with a team whether essentially making bundle writing serially executed (across the whole app) is acceptable, or you need a named lock.