-
Notifications
You must be signed in to change notification settings - Fork 361
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
Multiple processes sharing PINCache #2
Comments
No, it uses a runtime lock to protect file access. However, that sounds like a good enhancement to be made! |
Looked into using NSFileCoordinator a bit. One problem: This may be an issue with extensions as notifications for backgrounding don't occur if I'm not mistaken. |
Extensions do actually get little-known lifecycle notifications:
|
Ahh! Nice! The next concern I have is around performance. That's the next question to tackle :) |
Has this been implemented? |
To support notification center and Apple Watch extensions, we'd like to move our cache location to a shared app group container. However this enables multiple processes to simultaneously attempt to read and write on the same files. Does PINCache have any protection against this, by using NSFileCoordinator, for example?
The text was updated successfully, but these errors were encountered: