Alexander Mills

if client experiences error event there should be no more retries to acquire a lock

write broker in C

1

write broker in C

Give client setNoDelay option and give server setQuickAck

1

Give client setNoDelay option and give server setQuickAck see: https://www.extrahop.com/company/blog/2016/tcp-nodelay-nagle-quickack-best-practices/ https://eklitzke.org/the-caveats-of-tcp-nodelay

tcp fast open settings in ubuntu

1

https://blog.wasin.io/blog/2016/12/26/how-to-enable-fast-tcp-open-on-ubuntu.html

instead create a setTimeout, every 10 ms or so

If a certain client already has a lock on a key, e.g.: ``` client.lock('foo', ...); client.lock('foo', ...); ``` then why send it to the broker? just queue it in the...

Passing Infinity to lockp cannot acquire the lock at all, passing 800000 will run correctly

https://stackoverflow.com/questions/51352821/prevent-dev-branch-from-being-worked-on-locally

Upon uncaught exceptions in the broker 1. flip a boolean, and deny any incoming lock requests 2. remove all locks, then shutdown

Yo what's going on with the documentation

1

I am looking here: https://github.com/google/code-prettify and here: https://rawgit.com/google/code-prettify/master/examples/quine.html I see this example: ```html ``` note it has skin=sunburst as a query option param in the url.. so how do we...