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
Q: Use in a concurrent environment #529
Comments
Each destination has its own queue and SwiftyBeaver can be used in parallel environments. |
So they can write to the same file? No conflicts etc? Thanks. |
What file do you mean? |
i.e. using this: https://github.com/SwiftyBeaver/SwiftyBeaver/blob/master/Sources/FileDestination.swift |
ah you are using the FileDestination. It was actually initially just meant to be used for local macOS development. So you are right, it may lead to conflicts. |
Ok, then could you reopen this, as there is a way to implement it with the help of concurrent file operations (this is supported by the OS). |
good idea, reopening and asking for contributions to extend the usability of the FileDestination to more than 1 consumer. |
Hi, I'm curious whether it's allowed to use SwiftyBeaver in a concurrent environment. Let's consider we have 2 targets: an iOS app and an app extension, both are sharing the storage via the Shared Container.
Is there any limitation on whether we can log from both targets simultaneously? Should we implement the locking?
The text was updated successfully, but these errors were encountered: