Closed ebiiii closed 8 years ago
Did you schedule that for the next milestone (1.1.4)?
Well, yes I set the deadline for this task and assigned it to me... That's the part I wanted to improve first. Maybe we will only have the "MQwrapper" for next milestone and the full integration later. I'm also wondering about retro-compatibility.
Changed the deadline to next milestone and merged the zeromq wrapper implementation. It is not "reliable" yet, but improves a lot the performance.
Current experiments shows that it is reliable for "inproc" connections, but some stress tests are still needed to be sure it could be used instead of the local wrapper. In remote settings, it needs more testing... Moving to undefined milestone, as it will not replace those wrappers for back-compatibility reason until we go for a new major version.
Version 2.0.0 integrate zeroMQ as default for communication
Current version of the remote wrapper has some difficulties recovering when connection is lost. A system based on Message Queues should be implemented, using existing and tested solutions, such as RabbitMQ, ZeroMQ,... (cf. http://queues.io/) This can also be linked to the solution to the internal mesages queues.