madelson

> In terms of a lock escalation strategy, I think it would make sense to escalate in this mannor: This is what #38 is all about. The way I'm imagining...

> has this been tested / used with file shares I haven't tried this. The lock is based on .NET's exclusive stream locking which uses OS-level file locking under the...

Note to self: came across `WaitThread` in the runtime which offers a pattern we could follow for this.

> Question: is it a desire of this package to provide any kind of common IDistributedLock abstraction that all concrete providers will implement at a minimum? This is something I'm...

Hi @darkflame0 I am not actively working on this feature, just considering it. Can you help me understand your use-case? There are a few different ones I've considered: * In-memory...

@darkflame0 have you considered using `FileDistributedLock` or (if you are on windows) `EventWaitHandleDistributedLock`? These are both light-weight single-machine options.

@darkflame0 yeah different technologies offer different capabilities; I only implement when I think I can offer something robust and performant on top of the particular technology. Looking into it, I...

@darkflame0 I'm working on some prototypes for these. If I put out a prerelease version would you be interested in trying it out?

@darkflame0 ok prerelease is out (https://www.nuget.org/packages/DistributedLock.ProcessScoped/1.0.0-alpha01). Let me know if you get a chance to give it a try. This doesn't support composite locking yet, just the process-scoped named lock...

Hi @gtaylor44 thanks for reporting. Without more information it is going to be difficult to investigate the issue. In this situation, I can think of several possible options: * The...