W3C home > Mailing lists > Public > public-media-fragment@w3.org > March 2009

HTTP headers

From: Jack Jansen <Jack.Jansen@cwi.nl>
Date: Mon, 16 Mar 2009 15:54:04 +0100
Message-Id: <DE18B0CF-1953-4059-AFE1-7BF6592D4254@cwi.nl>
To: Media Fragment <public-media-fragment@w3.org>
Folks,
I've started with a client-side implementation of MF (the python  
urllib implementation that's on my plate), and implementing parsing  
goes pretty well: there's enough info in the draft to get something  
going.

Not so on the HTTP side, however.The 2way/4way document we have on the  
Wiki outlines the general idea, but nothing yet in the way of a  
specification of what the headers are, what their syntax is, etc.

I tend to be an implementation-driven guy, and what I've done so far  
has already uncovered some things in the client-side spec that has me  
raising an eyebrow, I think it would be good to do the same exercise  
for the protocol side. Doing an early implementation should allow us  
to fix warts before we go public.

So, my question is: when can we expect a first draft of the protocol  
spec that I could give a go at implementing?
--
Jack Jansen, <Jack.Jansen@cwi.nl>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma  
Goldman
Received on Monday, 16 March 2009 14:54:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 September 2011 12:13:32 GMT