[Standards] Proposed XMPP Extension: Stream Compression with Efficient XML Interchange

Peter Saint-Andre stpeter at stpeter.im
Mon Feb 18 03:56:07 UTC 2008


Fabio Forno wrote:
> On Feb 15, 2008 11:21 PM, XMPP Extensions Editor <editor at xmpp.org> wrote:
>> The XMPP Extensions Editor has received a proposal for a new XEP.
>>
>> Title: Stream Compression with Efficient XML Interchange
>>
>> Abstract: This document specifies how to use Efficient XML Interchange (EXI) in XML stream compression.
>>
>> URL: http://www.xmpp.org/extensions/inbox/compress-exi.html
>>
>> The XMPP Council will decide at its next meeting whether to accept this proposal as an official XEP.
> 
> Did some homework about EXI. I don't know if handling it as a
> compression method it's the best way, since it forces the client to
> have both an xml parser just for the first stanzas before features
> (indeed it could be done with some string search, but it's an ugly
> hack) and the exi parser. EXI streams, instead, have a starting header
> whose first two bits allow understanding whether the data is encoded
> with EXI or text xml, so a client wanting to use it could open the
> stream directly with EXI. If the servers doesn't understand it can
> reply with an error.

Alternatively, we could define a new SRV record that would enable a
deployment to advertise a different port for the EXI service, such as:

_xmpp-client-exi._tcp.example.com

Peter

-- 
Peter Saint-Andre
https://stpeter.im/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20080217/d4b75046/attachment.bin>


More information about the Standards mailing list