dominictarr / lock Goto Github PK

Something feels dirty about using multi threading primitives in a single threaded environment.

Maybe you should write a motivation section explaining the use-case.

Also how do other single threaded environments avoid the need for locking?

lock('key', function(unlock) { unlock()(); })

Currently, this is too convoluted. It should be:

lock('key', function(unlock) { unlock(); })

Hi. I found you package recently, and I can't do it works.

Take a look in my example:

lock('key', function (release) { //called when resource is available.
    console.log('executing block 1');
  //do an async operation, and wrap the callback with release.
  setTimeout(function() {
      console.log("releasing");
      release();
  }, 1000);
})

lock('key', function(release) {
    console.log("aqui");
});
setInterval(function() {
    console.log('interval');
}, 1000);

And the result:

executing block 1
releasing
interval
interval
interval

The lock in 'key' is kept later I called release.

Can you help me?

Hi there,

I'm getting the error 'Uncaught ReferenceError: setImmediate is not defined'.
I guess, author didn't expect that someone will use it in browser :)
Can we add extra check whether 'setImmediate' is available and use 'setTimeout' as a fallback solution?

Lock()(${id}, async (release) => {
try {
//
} finally {
release()
}
})

but not run when next call and release already invoked by before