Subject: Re: [hybi] [HyBi] MBWS Subprotocol

From: Hapner mark <[email-masked]>
Date: Thu, 12 Apr 2012 18:25:50 +0000

I haven't seen any feedback from the WG on the MBWS Subprotocol as yet. If anyone has any concerns or comments about its design or function please let us know. A registration request for the two Subprotocol names it defines has been submitted to IANA.

-- Mark
________________________________
From: Hapner mark
Sent: Tuesday, March 27, 2012 10:57 PM
To: [email-masked]
Cc: [email-masked]; [email-masked]; [email-masked]; Gaoyongguang; [email-masked]
Subject: [HyBi] MBWS Subprotocol

This version of the Message Broker Web Socket Subprotocols (MBWS and MBLWS)) has been revised to conform to RFC 6455's definition of a WebSocket Subprotocol. The purpose of this subprotocol remains the same - to add the metadata required to support a message queueing intermediary that allows clients to communicate via a shared set of message addresses without having to directly expose themselves to; or, know about the other clients of the intermediary.

Clebert and I would be very interested in HyBi's feedback on this draft. If there are no significant issues, we plan to register the two subprotocols it defines with IANA.

A binary binding is provided that allows binary WebSocket messages to transmit both binary and text subprotocol messages. A text binding for text WebSocket messages is defined for those applications that prefer to transmit only text.

http://www.ietf.org/id/draft-hapner-hybi-messagebroker-subprotocol-01.txt
http://www.ietf.org/id/draft-hapner-hybi-messagebroker-subprotocol-01.pdf
http://www.ietf.org/id/draft-hapner-hybi-messagebroker-subprotocol-01.xml