-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/1/12 10:28 AM, Jack Moffitt wrote: >> [A] I don't have much to add (a bit) about the protocol as far >> as data exchange is concerned (after having implemented the >> server part of it), but there >have been some requests around >> being able to multiplex multiple sessions/streams over the same >> websocket connection though. The rationale is that it would >> reduce the # of simultaneous connections that the server has to >> handle. This because especially important with websockets since >> the connections are persistent, so even idle clients consume >> resources (actually this is true even for BOSH since connections >> are constantly established & broken even for idle clients). > > Two things here: > > MUXing is something the websockets group was working on, so I > assume it's going to be done at the layer below as a transparent > browser optimization. I think it's out of scope to put muxing in > the websockets XMPP encoding.
Yep: https://datatracker.ietf.org/doc/draft-ietf-hybi-websocket-multiplexing/ Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCSpWUACgkQNL8k5A2w/vxIDACcCy9SbkJxOuAbIQz9F9pdZePQ WI8An0SHy0lZzMW6enKp/mG19Oy6iZCh =xZ/z -----END PGP SIGNATURE-----
