You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if it were since the underlying HttpClient is, but if that requires too much effort, perhaps a line in the documentation clarifying the library's thread safety would be helpful.
The text was updated successfully, but these errors were encountered:
I am admittedly not as well experienced/read in thread-safety as I could be. I am not sure of the changes require and their extensiveness to be completely thread-safe. I will have to do some research.
From my brief review of the library's internals, I didn't notice many thread safety issues - the only glaring one I noticed is the way that the B2Options class is used to pass state around in several places, and that can probably be easily avoided by passing context on the stack instead (e.g. passing the upload authorization token directly to FileUploadRequestGenerators.Upload as an argument).
Of course, the simplest approach to start would just to be document that the library is not thread-safe. 😂
I'm guessing it is not because of things like this:
B2.NET/src/Files.cs
Line 124 in 07d3f74
It would be nice if it were since the underlying
HttpClient
is, but if that requires too much effort, perhaps a line in the documentation clarifying the library's thread safety would be helpful.The text was updated successfully, but these errors were encountered: