advisory-lock
advisory-lock copied to clipboard
Detect "in process" collisions comment
Hi,
I've read the code and noticed the following comment: // TODO: detect "in process" collisions?
Can you explain if its relevant so I can create PR to fix it? what are these in-process collisions that can occur?
As far as I understand, when creating a hash there is "near-unique" number. If creating lock for the same string multiple times, multiple lock objects will be created, but they all going to function appropriately with their database interactions.
Hi, just letting you know I moved the repo to https://github.com/binded/advisory-lock and fixing bugs.