On Aug 31, 2008, at 11:57 AM, Markus KARG wrote:
> HTTP/1.1 describes the technique of applying transfer encodings for
> compressed transmission of entities. I would like to know whether
> Jersey is supporting that in any way.
> Will the Jersey server side automatically negotiate and apply
> compression, and will the client API suggest and apply decompression?
Not currently. Also, when the client sends something it can apply
compress.
This would be a job for filters.
I also need to refactor the client API to make it easy/possible to
adapt the Input/OutputStreams.
> Is that planned for a future release?
>
Could you log an issue?
Thanks,
Paul.