[zeromq-dev] Websockets as a Transport ?

[Mark Farnan]

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.

This, or something similar, is what I am thinking.   (You can actually do
all of this in one step with a http connect and upgrade frame)

So ideally a client would provide the address,  i.e.
"wss://someserver.someplace.com/something", to the Socket Connect function,
along with an optional username and PW,      It establishes the session, and
ZeroMQ works as before from there.

The ZeroMQ receiving the connection would need a registered callback of some
kind to handle  the authentication, which just passes back 'true or false'
if its accepted or not. 


Would anyone else maybe interested in doing this ?

Regards

Mark

-----Original Message-----
From: zeromq-dev-bounces at lists.zeromq.org
[mailto:zeromq-dev-bounces at lists.zeromq.org] On Behalf Of Paul Colomiets
Sent: Thursday, July 05, 2012 3:03 PM
To: ZeroMQ development list
Subject: Re: [zeromq-dev] Websockets as a Transport ?

Hi Mark, Ian,

On Thu, Jul 5, 2012 at 12:44 AM, Ian Barber <ian.barber at gmail.com> wrote:
>> I'm evaluating zeroMQ, and one main criteria we have is to support 
>> Websockets for client to server communications.
>>
>>
>>
>> Has there been any work on making a native Websocket transport for 
>> ZeroMQ in the core C++ libraries ?
>
>
> No work that made it anywhere near head, but as Apostolis said there 
> are plenty of bridging methods. My personal favourite is Paul's ZeroGW:
> https://github.com/tailhook/zerogw
>

Thanks Ian, I appreciate your respect :) However, zerogw is designed with
browser clients in mind. Mark's use case may be a bit different.
Although, I would support usage of zerogw for other applications, but I'm
not going to implement outbound websocket connections at the current stage
of evolution of zerogw, so you need some complementary client
implementation.

--
Paul
_______________________________________________
zeromq-dev mailing list
zeromq-dev at lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev