{"push_id":968068143,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"ad925e46717a952dae50c2a40dee777a00466cec","before":"1cc3b9c80e948b5f7052ac76f03d31a143269cf6","commits":[{"sha":"2ae4f8faf3af845f4fac4fe768c9911f728fd9ba","author":{"email":"f07530a1aaf02c33041f9951878488e424a906c8@mirantis.com","name":"Oleksii Zamiatin"},"message":"[zmq] Use PUSH/PULL for direct CAST\n\nIn order to complete implementation of the spec [2]\nand for optimal zmq-way patterns usage. By zmq-way\nmeaning some relaxed guarantees on reliability, but\nhigh performance and scalability. PUSH/PULL for CASTs\nhere gives us benefit of not having redundant\nbackward tcp-connections which DEALER/ROUTER opens.\n\nOpposite to that there is another approach provided\nby spec [1]. This approach has strong gurantees on\nmessages delivery based on acknowledgements and retries.\nSuch approach has lower performance though.\n\nThe general idea is to provide both approaches in the\ndriver and switch between them in configuration.\n\n1. https://review.openstack.org/#/c/171131/\n2. https://review.openstack.org/#/c/187338/\n\nChange-Id: I32712f73e2ec4114406641de5aec3b12152ad58f","distinct":true,"url":"https://api.github.com/repos/openstack/oslo.messaging/commits/2ae4f8faf3af845f4fac4fe768c9911f728fd9ba"},{"sha":"ad925e46717a952dae50c2a40dee777a00466cec","author":{"email":"d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","name":"Jenkins"},"message":"Merge \"[zmq] Use PUSH/PULL for direct CAST\"","distinct":true,"url":"https://api.github.com/repos/openstack/oslo.messaging/commits/ad925e46717a952dae50c2a40dee777a00466cec"}]}