[Grub-dev] LZMA support in upload server

[Balinny]

Jeremie Miller wrote:
> When we get a new dispatch, it could easily just detect the incoming  
> Accept-Encoding header and take the top one as the preferred... the  
> idea being though that there needs to be a way to enforce the  
> compression of the arcs before they're uploaded.
>
> Jer
>   
Of course, we would forbid the identity encoding :)

> > It's a two-minute change. Specially given that the last entry must be
> > generated on-the-fly anyway.
>   
>
> That same like run again new workunits with Accept header ;) If i good
> count, this 2 minutes take now around 1 month ;) 
Workunits are pre-generated, but I think the last entry (containing the
user name) is made on request?

> Unfortunately Jeremie
> don't have free time for made any changes in current dispatch server.
> So probably this 2 minutes task must wait few months before i start
> work on new dispatch server (at this moment i don't have access to
> dispatch server).
>   
What really does the dispatch server? Which interface does it use to
grab the urls?

>> As a bonus, also add  Accept-Encoding: gzip, lzma
>>     
>
> 1. Where add it?
>   
To the last workunit entry.

> 2. IIRC LZMA isn't registered compression for any HTTP version and
> cannot be placed in HTTP headers.
>   
Neither is bzip2 or sdch.
Treat that as an extension to the protocol :)