Re: [packaging-on-the-web] Why not use `Content-Encoding`? (#17)

> Content-Encoding is a description of the actual content, so decoding it is part of handling to body. Transfer-Encoding means that the body needs to be decoded prior to its handling (like if it was a transient serialization).

Isn't each part a body of its own? e.g. `Content-Type` also refers to the entity-body.

> Also compressing the whole passage means that you need to decompress everything instead of just skipping until the next boundary and process only what you need.

I agree "seek"-like functionality is not possible without full decompression. That's not what issue 3 is saying though. It talks about "streamability" which I understand as streamed decoding, which is possible.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/packaging-on-the-web/issues/17#issuecomment-69360615