- From: Mark Nottingham <mnot@mnot.net>
- Date: Fri, 9 Apr 2010 13:17:57 +1000
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
Hmm, IETF doesn't appear to have a liaison with the JCP. I did find this: http://java.sun.com/j2se/1.5.0/docs/guide/deployment/deployment-guide/pack200.html ... where it's pretty clear this is an abuse of Accept-Encoding. I'd hazard a guess that it's deployed somewhat; can some of the more Java-minded people on the list ask around, please? To me, this seems like a good argument for a slightly higher bar in this registry... and I'm sorely tempted to try to remove this entry, or at least deprecate it, if it's already deployed. On 08/04/2010, at 11:25 PM, Julian Reschke wrote: > Hi, > > I was looking at the content coding IANA registry (<http://www.iana.org/assignments/http-parameters>) and decided to see what pack200-gzip: > >> pack200-gzip Network Transfer Format for Java Archives [JSR200] > > is about. > > From what I understand this is a format similar to ZIP/Jar, in which you have a directory structure with named entries. How exactly is this supposed to work as HTTP Content Coding then? > > Has anybody seen this in the wild? Is anybody aware of implementations? > > Best regards, Julian > > -- Mark Nottingham http://www.mnot.net/
Received on Friday, 9 April 2010 03:18:29 UTC