On 20 March 2011 09:09, Pieter Hintjens <[email protected]> wrote: > On Sat, Mar 19, 2011 at 9:21 PM, John W Higgins <[email protected]> wrote: > > >> This is neat. It's something lots of people have discussed making but > >> no-one's actually done. > > > > Zed Shaw has a very nice implementation baked into the Mongrel2 web > server > > (http://mongrel2.org/home). > > Mongrel2 is excellent, and I didn't mean to ignore it... I think the > question here is rather, "how do I extend my 0MQ network across the > Internet" rather than "how do I build my web services using 0MQ"... >
So the focus is on using HTTP as a transport protocol, between zeromq peers, not intended to be used as an interoperability solution, did I understand correctly? I suppose that the advantages of having a HTTP transport would be at least: 1. pass through firewalls (useful for end user applications which have to be able to run behind networks which open only port 80 for outbound connections) 2. allow to multiplex traffic of multiple zmq sockets by using the extra level of addressing (paths) offered by http over the same port (or tcp even connection, by using keep-alive) 3. leverage existing middleware, like proxies, reverse proxies, load balancers etc, designed for http which might offer features not provided by current zmq devices or simply the user could find them as the right tool to use (because it's already provided in their environment, for example cloud solutions etc) Are there other reasons to use HTTP as a transport for 0mq? Cheers, Marko
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
