[zeromq-dev] Websockets as a Transport ?

[Mark Farnan]

Thanks for the quick reply.

 

I'll take a look at VTX.

 

Sadly, we already know that using ZeroMQ on Port 80/443 won't fly at all.
Been down this road already with trying to use a TCP socket on these ports.


Regards

 

Mark Farnan

Director, Product Development

Petrolink Services Inc

+1 281 908 9814

 

From: zeromq-dev-bounces at lists.zeromq.org
[mailto:zeromq-dev-bounces at lists.zeromq.org] On Behalf Of Ian Barber
Sent: Thursday, July 05, 2012 6:27 PM
To: ZeroMQ development list
Subject: Re: [zeromq-dev] Websockets as a Transport ?

 

 

On Thu, Jul 5, 2012 at 11:53 PM, Mark Farnan <mark.farnan at petrolink.com>
wrote:

Correct,  What I am after is a bit different.

I am looking for using Websockets as native transport,  machine to machine
running ZeroMQ natively at each end, across firewalls.   For our case we
can't rely on a TCP port being open to work through.  Websockets provides
the ideal transport protocol for this.

i.e.
 Connects Https
 Handles Security (even  basic Auth is fine, as it is HttpS).
 Upgrades the connection to Websocket  wss
 ZeroMQ runs 'as is' over the now established Websocket.

 

It's a non-trivial bit of work to implement a new transport, but it's
definitely an option. I'll doubt you'll get someone willing to jump in and
do it unless someone is quietly already working on it though, as it'd be a
fair investment of time. If you're interested in doing it yourself though
people here can certainly point you in the right direction. 

 

Other options worth considering would be:

 

1 - Pieter's VTX: https://github.com/imatix/vtx - this is designed to be an
easier way of adding extra protocols, building on top of the existing zeromq
library. 

2 - Running ZeroMQ TCP across port 80 or 443. Depending on the firewall
config, you might find this is enough to get the traffic through and will
get you up and running with a lot less effort. YMMV. 

 

Ian

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20120705/deebe02b/attachment.htm>