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
We currently use the last release (but still non stable) version '1.0 beta 5' of Microsoft Azure Java SDK.
Indeed, Microsoft announced that it is only a developer preview but which already supports major parts of the SDK.
Regarding thread-safety, it seems there is no garantee:
We do not make any thread-safety guarantees about our libraries. We also do not test them for thread-safety.
Methods that are currently thread-safe may be thread-unsafe in future versions.
The AzureProvider class has been however tested by us and the SDK classes we are using are actually thread safe.
However this need to be carefully double-checked after every SDK upgrades, as mentioned by Microsoft devs.
The text was updated successfully, but these errors were encountered:
We currently use the last release (but still non stable) version '1.0 beta 5' of Microsoft Azure Java SDK.
Indeed, Microsoft announced that it is only a developer preview but which already supports major parts of the SDK.
Regarding thread-safety, it seems there is no garantee:
The AzureProvider class has been however tested by us and the SDK classes we are using are actually thread safe.
However this need to be carefully double-checked after every SDK upgrades, as mentioned by Microsoft devs.
The text was updated successfully, but these errors were encountered: