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
However, the implicit call to Dispose is doing a synchronous db call and blocking the calling thread so I'd love to see an option to dispose asynchronously, even if it means I can't use the using keyword in my calling code.
I guess SqlDistributedLock .TryAcquireAsync could return an interface like this:
Hi @clement911 thanks for the suggestion. I agree that this is a good idea. A few thoughts:
Changing this would be a binary breaking change, so we would have to do it as part of a 2.0 release
It looks like .NET Core is working on a standard IAsyncDisposable interface for this (https://github.com/dotnet/corefx/issues/32640), so I would want to wait for that to be released and understand the implications of it (e .g. can you use it in a using block?) before building this.
Finally, some lock releases can't benefit from async (e. g. transaction-based locks release with SqlTransaction.Dispose(), which isn't async. That said, (a) maybe this will change when IAsyncDisposable comes out and (b) it doesn't stop us from implementing the interface for the cases where we will get the benefit.
The
using
pattern is nice and reads very well.However, the implicit call to Dispose is doing a synchronous db call and blocking the calling thread so I'd love to see an option to dispose asynchronously, even if it means I can't use the
using
keyword in my calling code.I guess
SqlDistributedLock .TryAcquireAsync
could return an interface like this:What do you think?
The text was updated successfully, but these errors were encountered: