EXI for HTTP? Re: Efficient XML Interchange (EXI) LC spec addresses ISSUE-30 (binaryXML-30)?

Tim,
 
We've done a fair bit of thinking about this and -- surprise, surprise --
think its a pretty good idea. As you know, EXI is more than "XML
compression". It is a generic technique for encoding just about any kind of
data -- even packed binary protocols -- more efficiently. However, unlike
custom protocols like SPDY, it works with the XML stack of technologies and
XML toolchain. So, rather than introducing more complexity, more code and
another stack of technologies, it enables more components to leverage the
existing stack -- increasing interoperability and expanding the XML
community. 
 
Based on my experience, I'm certain an EXI-based approach would be more
efficient than the gzip approach used by SPDY. Let me know if you'd like to
explore this. I'd be happy to discuss and help. 
 
    All the best,
 
    John 
 
 
From: Tim Berners-Lee <timbl@w3.org
<mailto:timbl@w3.org?Subject=Re%3A%20EXI%20for%20HTTP%3F%20%20%20Re%3A%20Eff
icient%20XML%20Interchange%20(EXI)%20LC%20spec%20addresses%20ISSUE-30%20%20(
binaryXML-30)%3F&In-Reply-To=%253CBECE1DC9-1EF1-4571-905F-35DCA5B22473%40w3.
org%253E&References=%253CBECE1DC9-1EF1-4571-905F-35DCA5B22473%40w3.org%253E>
> 
Date: Sat, 5 Dec 2009 12:35:12 -0500
Cc: Dan Connolly <connolly@w3.org
<mailto:connolly@w3.org?Subject=Re%3A%20EXI%20for%20HTTP%3F%20%20%20Re%3A%20
Efficient%20XML%20Interchange%20(EXI)%20LC%20spec%20addresses%20ISSUE-30%20%
20(binaryXML-30)%3F&In-Reply-To=%253CBECE1DC9-1EF1-4571-905F-35DCA5B22473%40
w3.org%253E&References=%253CBECE1DC9-1EF1-4571-905F-35DCA5B22473%40w3.org%25
3E> >, www-tag@w3.org
<mailto:www-tag@w3.org?Subject=Re%3A%20EXI%20for%20HTTP%3F%20%20%20Re%3A%20E
fficient%20XML%20Interchange%20(EXI)%20LC%20spec%20addresses%20ISSUE-30%20%2
0(binaryXML-30)%3F&In-Reply-To=%253CBECE1DC9-1EF1-4571-905F-35DCA5B22473%40w
3.org%253E&References=%253CBECE1DC9-1EF1-4571-905F-35DCA5B22473%40w3.org%253
E>  
Message-Id: <BECE1DC9-1EF1-4571-905F-35DCA5B22473@w3.org> 
To: Robin Berjon <robin@berjon.com
<mailto:robin@berjon.com?Subject=Re%3A%20EXI%20for%20HTTP%3F%20%20%20Re%3A%2
0Efficient%20XML%20Interchange%20(EXI)%20LC%20spec%20addresses%20ISSUE-30%20
%20(binaryXML-30)%3F&In-Reply-To=%253CBECE1DC9-1EF1-4571-905F-35DCA5B22473%4
0w3.org%253E&References=%253CBECE1DC9-1EF1-4571-905F-35DCA5B22473%40w3.org%2
53E> > 

By the way, has anyone looked at using EXI for HTTP and MIME?

Toward solving the problems of always sending the same darn HTTP  

headers...

One wouldn't normally suggest it but as Google seem to think spdy is  

better in binary, maybe a common interchange format would be a good  

idea....



On 2009-11 -25, at 05:34, Robin Berjon wrote:



> On Nov 25, 2009, at 04:32 , Dan Connolly wrote:

>> That is: I propose that the EXI spec of 19 Sep

>> addresses TAG issue binaryXML-30.

>> http://www.w3.org/2001/tag/group/track/issues/30

>

> Woo-hoo! Are there plans to throw a party of sorts?

>

>> Efficient XML Interchange (EXI) Format 1.0

>> W3C Working Draft 19 September 2008

>> NOTE: This is the Last Call working draft.

>

> Note that this is to be a CR very soon, I believe.

>

> -- 

> Robin Berjon - http://berjon.com/

>
CTO, AgileDelta, Inc.
 <mailto:john.schneider@agiledelta.com> john.schneider@agiledelta.com
 <http://www.agiledelta.com/> http://www.agiledelta.com
w: 425-644-7122
m: 425-503-3403
f: 425-644-7126