Scott Francis

> While clashes are fairly unlikely with SHA1, (1 in 4 billion with a 32 bit key_t), a guarantee that a clash won't happen is even better `ftok` isn't bulletproof...

Perhaps we could do something like store a mapping of all active `resource_id` -> `sem_id`s in a hash to detect collisions? It seems unlikely that we would encounter one, but...

I think I'd be fine with this as well.

My big concern with this implementation is the number of shared memory segments that will be created. It looks like we're using distinct shared memory segments for each instance of...

We built a version of this for an internal production engineering hack days recently at Shopify. We took a very different approach. [`ngx.semaphore`](https://github.com/openresty/lua-nginx-module#ngxsemaphore) was introduced in lua-nginx-module v0.10.0. Each nginx...