[zeromq-dev] Fwd: [hybi] hum #3: Message
sustrik at 250bpm.com
Mon Aug 9 18:40:04 CEST 2010
Pieter Hintjens wrote:
> FYI and as part of the slow but inevitable process of turning 0MQ's
> wire level protocols into a real specification for interoperability,
> here is the state of the framing discussion for WebSockets, which is
> an asynchronous message carrying protocol. Closer to TCP than
> anything else but what interests me is the proposed framing format:
> 1 bit - fragment
> 2 bits - reserved
> 5 bits - opcode
> 8 bits - short length
> [if length = 255: 6 bytes length]
> length bytes of payload
> IMO it would be desirable if (a) IETF WebSockets used a framing format
> close to what 0MQ does, for efficiency reasons and (b) if 0MQ adopted
> the final IETF WebSockets framing format, if it remains this similar.
> Using an IETF-standard framing format would make the 0MQ wire-level
> protocol a lot more compelling.
Fair enough. Let me answer on hybi list.
More information about the zeromq-dev