Vadim Gritsenko wrote:
Pier Fumagalli wrote:
On 17/3/03 20:15, Stefano Mazzocchi [EMAIL PROTECTED] wrote:
snip/
What about adding a 'content encoding' attribute to the 'pipeline'
instead?
'transfer encoding' attribute would make sense, but content encoding...
wait wait wait
I'm using
Stefano Mazzocchi wrote:
Vadim Gritsenko wrote:
Pier Fumagalli wrote:
On 17/3/03 20:15, Stefano Mazzocchi [EMAIL PROTECTED] wrote:
snip/
What about adding a 'content encoding' attribute to the 'pipeline'
instead?
'transfer encoding' attribute would make sense, but content encoding...
Sorry for the subject ... I was intended on another kind email, but when I
realized that I still had a couple of gray areas that I wanted to address, I
rewrote it forgetting the title...
Pier
Pier Fumagalli wrote:
On 17/3/03 20:15, Stefano Mazzocchi [EMAIL PROTECTED] wrote:
snip/
What about adding a 'content encoding' attribute to the 'pipeline' instead?
'transfer encoding' attribute would make sense, but content encoding...
Currently pipeline does not alter content, does
