Moein Nemati
Moein Nemati
PR: #1333
@madelson Hi! Sorry for the delay - I was busy and totally forgot about this. I've now resolved all the comments and added the tests as discussed. The PR should...
Thanks @madelson for the reply! I was initially considering **Approach 1** (composite IDistributedLock instances) for its simplicity and flexibility. However, I understand your point about the inefficiency of multiple round-trips....
Thanks @madelson! After thinking it through, I don’t find any issues using multi-key locks with multi-round-trips (composite IDistributedLock instances) for our use case, aside from the added latency. Since it’s...
@madelson That totally makes sense and is suitable for our use case. And we are already using provider instance. Thanks!
@madelson Sorry I wasn’t able to work on this until the weekend. After running some tests, here’s what I’m proposing: - Composite handle Introduce CompositeDistributedSynchronizationHandle (implements IDistributedSynchronizationHandle) that wraps multiple...
@madelson That all makes sense. The only concern left for me is the `IDistributedSemaphore` and `IDistributedUpgradeableReaderWriterLock` helper implementations since they have different method signatures than others: - `IDistributedSemaphore` helpers take...
@madelson Any thoughts on this?
Yes. Thanks @madelson #248 is up for review.