[Standards] draft-ietf-xmpp-websocket-10

Hund, Johannes johannes.hund at siemens.com
Fri Oct 10 06:55:21 UTC 2014

The current XEP is of course geared towards TCP/TLS connection and forsees two Mechanisms:

-        Different exi-specific port

-        Reopening the stream in-band (reusing compression semantic)

The second one would be possible technically, yet would violate the RFC.
But you’re right, the first one would still work (using your suggestion).

Von: Standards [mailto:standards-bounces at xmpp.org] Im Auftrag von Dave Cridland
Gesendet: Donnerstag, 9. Oktober 2014 18:03
An: XMPP Standards
Betreff: Re: [Standards] draft-ietf-xmpp-websocket-10

On 9 October 2014 15:26, Hund, Johannes <johannes.hund at siemens.com<mailto:johannes.hund at siemens.com>> wrote:
One point that I do realize now (too late) is that this means it's not possible to use EXI (XEP-0322) over websocket, right?
It's basically a 1:1 binary representation of the information in an XML structure/document and therefore definitely not UTF-8.

I would have thought that you'd want to negotiate an EXI session differently at the HTTP/WebSocket layer anyway, surely?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20141010/45d4ebbb/attachment.html>

More information about the Standards mailing list