{"push_id":634453068,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"48acf3e6b6ecf993c1e6038c92a172a4ced81cf8","before":"9ef95b0fac5d5919df6ac4a47c7fd0a192ebed0c","commits":[{"sha":"daf21b03b557cc86129ec2c52453ca6188045b51","author":{"email":"9980aac90228f366d2606242a5f07d3e32b806a8@users.noreply.github.com","name":"zbierak"},"message":"Cryptography manager optimizations\n\nJobQueue now stores a pointer to CryptoJob instead of a full structure for faster processing","distinct":true,"url":"https://api.github.com/repos/zbierak/bento/commits/daf21b03b557cc86129ec2c52453ca6188045b51"},{"sha":"48acf3e6b6ecf993c1e6038c92a172a4ced81cf8","author":{"email":"9980aac90228f366d2606242a5f07d3e32b806a8@users.noreply.github.com","name":"zbierak"},"message":"Communication between crypto manager and main thread is performed via shared queue\n\nThe previous communication, i.e. sending cryptography response, has been performed via zmq channels and in some situations might drop messages due to queue overflow, leading to deadlock in client programs. Right now the zmq channel is only used to transmit a single notification byte, and the rest is stored in a JobQueue inside CryptoManager and is removed in the Node main loop","distinct":true,"url":"https://api.github.com/repos/zbierak/bento/commits/48acf3e6b6ecf993c1e6038c92a172a4ced81cf8"}]}