[zeromq-dev] Websockets as a Transport ?

[Bennie Kloosteman]

Hi Mark,

Web socket uses tcp underneath so getting through the firewall is no issue
just use port 80  , and in fact web sockets ( and things that use port 80 )
have issues with some ISP html proxy servers and load balancers and it will
take time for these products to mature to handle web sockets.

AFAIK web sockets is also client to server and most clients already have
open all ports out and few in , if you want in a solution like Microsoft
Azure uses is ideal ( they have a tcp connection , it tries to open a
firewall port to receive and if it fails it relays it via the cloud - but
in the best case you have direct client to client connections)

 I would not trust https too much it does not add a lot , make sure the
authentication is good.

Also  by the time you add the higher level costs like encryption what is
the point to using a light weight protocol  like zeromq ? You may as well
use a nice API like WS-Eventing  which can still do 3ms  packets  (
100Kpackets/sec per server)

Ben

On Fri, Jul 6, 2012 at 6:53 AM, 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.
>
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20120706/5a03d588/attachment.htm>