Re: Proposal for including EXI in XMPP

Peter,

Its really great to see some momentum on this! Thanks very much for the
energy you are putting into it. This is something in which I've had a
long-running interest. In fact, I think Peter and I first talked about it
back in 2005 (yikes!). Although I'm not sure Peter was completely sold on
the idea at the time (broccoli ice cream anyone? [1]), he was gracious
enough to help us get the XMPP EXI use case together [2] and even started an
early draft [3]. Thanks Peter! ;-)

Here at work, we have incorporated EXI into various XMPP solutions to
support our Efficient XML users (e.g., to enable XMPP on aircraft). So, I'm
very interested in following your progress. Please keep me in the loop as
you move forward. I'd be very happy to help if I can.

All the best!,

John

AgileDelta, Inc. 

john.schneider@agiledelta.com <mailto:john.schneider@agiledelta.com>

http://www.agiledelta.com <http://www.agiledelta.com>


[1] 
http://pooh-99hi.blogspot.com/2005/11/peter-saint-andre-broccoliafter.html
[2] http://www.w3.org/TR/xbc-use-cases/#xmpp
[3] file:///jcs/Work/Standards/XMPP/xep-0000-Exi.html


From:  Peter Waher <Peter.Waher@clayster.com>
Date:  Thursday, March 14, 2013 7:38 AM
To:  FABLET Youenn <Youenn.Fablet@crf.canon.fr>, "public-exi@w3.org"
<public-exi@w3.org>
Cc:  "Joachim Lindborg (joachim.lindborg@sust.se)"
<joachim.lindborg@sust.se>, Yusuke DOI <yusuke.doi@toshiba.co.jp>, Peter
Saint-Andre <stpeter@stpeter.im>, XMPP Standards <standards@xmpp.org>,
"mact-usa@att.net" <mact-usa@att.net>, Stephen Williams <sdw@lig.net>
Subject:  RE: Proposal for including EXI in XMPP
Resent-From:  <public-exi@w3.org>
Resent-Date:  Thu, 14 Mar 2013 14:39:02 +0000

Dear Youenn,
 
Thank you for your response.
 
We also think EXI is exceptionally interesting and want to use it for other
technologies as well. For instance, we are also looking at EXI compression
in REST web services, especially for use with mobile devices hoping to
improve latency by decreasing packet sizes.
 
Regarding using the preexisting EXI option header, I was also thinking the
same thing in the beginning, but changed my mind thinking there are options
that are not readily applicable in the XMPP case (for instance the
Document/Fragment option), as well as options that are necessary in the
EXI/XMPP case that are not applicable and available in the more general EXI
case, such as the sessionWideBuffers option, added in revision 0.0.2. (I¹ve
attached the latest revision, with a note regarding this option §3.2).
 
Thank you for your time, and looking forward to your comments,
Sincerely,
Peter Waher
 
 

From: FABLET Youenn [mailto:Youenn.Fablet@crf.canon.fr]
Sent: den 14 mars 2013 11:00
To: Peter Waher; public-exi@w3.org
Cc: Joachim Lindborg (joachim.lindborg@sust.se)
Subject: RE: Proposal for including EXI in XMPP
 
Hi,
 
That is an interesting piece of work.
My first thought when going through it is that EXI option negotiation may be
a feature that is useful to more than XMPP.
That is very good that you bring it to the table.
 
Reading the spec quickly, I wonder whether the already-defined EXI header
option element could be used for that purpose, especially in the case it can
be serialized as EXI.
 
Anyway, I think the EXI WG will review this and get back to you.
Regards,
                Youenn
 

From: Peter Waher [mailto:Peter.Waher@clayster.com]
Sent: mercredi 13 mars 2013 17:43
To: public-exi@w3.org
Cc: Joachim Lindborg (joachim.lindborg@sust.se)
Subject: Proposal for including EXI in XMPP
 
Hello
 
We have made a first draft of a proposal for incorporating EXI into XMPP
networks. (See attached files.)
 
Anybody with an interest in EXI & XMPP are welcome to join us in this
effort, please contact us. Any comments, suggestions, etc., on the contents
of these documents are warmly welcomed and appreciated.
 
Sincerely,
Peter Waher