- From: Eliezer Croitoru <eliezer@ngtech.co.il>
- Date: Sun, 03 Feb 2013 21:47:00 +0200
- To: ietf-http-wg@w3.org
On 2/2/2013 1:53 PM, Roberto Peon wrote: > I'll point out that the delta compressor already deals these encoding > problems by using a static dictionary (i.e. O(1) state for program > execution) for key-values, some of which are certainly ":method", "GET", > etc... > > Thus the various methods get assigned numeric IDs, and if one isn't > familiar, then you can either represent it as text every time, or if the > receiver allows for state storage, it can allocate a new numeric ID > after seeing the method once. > > The only thing that isn't "solved" right now is putting the scheme, > host, and path components in whatever combination, at the beginning, > mainly because it makes the state machine for a(ny) compressor > significantly more annoying to manage as it can require that entries in > the compression context get expired. > > If we're worried about the bit-width of these things, we can make some > of these "special" and only use a byte to index 'em (thusfar the static > dictionary has ~64 items, so this should be quite safe). Personally, I > hate that idea, and think that 2-bytes to encode this is perfectly fine. :) > > -=R > I was just wondering about what is the proposal for now? -- Eliezer Croitoru http://www1.ngtech.co.il
Received on Sunday, 3 February 2013 19:47:45 UTC