Hello, I've tried reading as much as I can about this but couldn't find quite the answer to my question in docs.
My plan is to use a multiple mongrel2 servers pointing to a cluster of handlers written in python by me (they are very simple endpoints), which will then forward the requests into a cloud of python actors for processing via zmq PUSH sockets (so it's a pipeline, not a req/rep), the response needs to be eventually sent back to the right mongrel2 server for response. The messages as they transit through the cloud will keep the original envelope parameters required to be sent back to the correct mongrel2 server. The problem I am seeing is that the Mongrel2 servers' response endpoint is a SUB (that's fine) in BIND mode. If it was in CONNECT mode I would simply point all the connection strings towards a XSUB/XPUB device to do the many-to-many PUB SUB between the Mongrel2 servers and handlers. The only thing I could think of but could not find an example anywhere is that I can indeed do multiple "connect_out" calls on the zmq device, once for each Mongrel2 server. All the examples of device I see do a single bind_in and bind_out call (or connect_), never more than one. Maybe I am missing something, maybe it's a zmq question really, but I'd like to see some sample backend architectures to be used with Mongrel2 handlers. Any comments, thought? Thanks
