[zeromq-dev] ZMQ_WEBSOCKET - any work in progress?

[Michael Haberler]

I found a starting point for what I want - libwebsockets/zmq bridging in C++:

https://github.com/dsoo/shardfree

very early, very c++11ish, but a cheatsheet to start from

-Michael


Am 11.08.2013 um 14:47 schrieb Michael Haberler <mail17 at mah.priv.at>:

> 
> Am 11.08.2013 um 02:09 schrieb Justin Karneges <justin at affinix.com>:
> 
>> On 08/09/2013 10:50 AM, Michael Haberler wrote:
>>> 
>>> Am 27.06.2013 um 20:58 schrieb Pieter Hintjens <ph at imatix.com>:
>>> 
>>>> So ZMQ_STREAM is now a usable socket type for TCP clients and servers,
>>>> and I've made a test case that shows simple a HTTP ping-pong, in
>>>> tests/test_stream.cpp.
>>> 
>>> I think it's a great idea!
>>> 
>>> Is anybody planning/working on a similar idea for websockets (maybe using the libwebsockets.org code)?
>> 
>> You could just use ZMQ_STREAM to talk to a websocket client/server. IMO, 
>> anything beyond what is supported by 0MQ should be the job of a gateway 
>> worker. Websockets would be in the realm of Mongrel2, ZeroGW, Zurl, etc.
> 
> I am aware of the available gateway process solutions. I do not like them for the extra process and extra context switches involved, which doesnt exactly improve latency. A in-process solution with worker threads would be fine though.
> 
>> Even ZMQ_STREAM smells like feature creep ("send and receive from a 
>> non-0MQ peer" - what the what?). But everyone loves a good raw mode.
> 
> I dont concur on the 'feature creep' view. That is rather basic interoperability - you can't expect the rest of networking applications to all become ZMQ-aware.
> 
> - Michael
> 
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev