hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Abley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HTTPCLIENT-834) Transparent Content Coding support
Date Tue, 04 Aug 2009 21:29:10 GMT

     [ https://issues.apache.org/jira/browse/HTTPCLIENT-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Abley updated HTTPCLIENT-834:
-----------------------------------

    Attachment: disable-content-coding.patch

Speculative patch to show how it could be disabled. If this was decided as a reasonable way
to go, then the ContentEncodingProcessor would need to be made public and put into a different
package, to highlight that it is part of the published API. I still strongly feel that this
behaviour should be enabled by default, but it is also necessary to give us the out of turning
it off. Is the special case shown here worthwhile, or could it be accomplished in another
way?

Also added some additional filtering for the Content-Encoding header in the response - if
the ResponseProcessor handles it, then we should probably remove the existence of that header
from the client application.

> Transparent Content Coding support
> ----------------------------------
>
>                 Key: HTTPCLIENT-834
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-834
>             Project: HttpComponents HttpClient
>          Issue Type: New Feature
>          Components: HttpClient
>    Affects Versions: 4.0 Beta 2
>         Environment: Any
>            Reporter: James Abley
>             Fix For: 4.1.0
>
>         Attachments: 834-2009-03-17.patch, 834-svn-754998.patch, disable-content-coding.patch
>
>
> I would like to see HttpClient features brought up to parity with other libraries, both
in Java and other languages. c.f. Python's httplib2 (not yet in the standard library, but
many would like to see it in there). That library transparently handles gzip and compress
content codings.
> This issue is to capture possible solutions to providing this sort of innate functionality
in HttpClient, so that users aren't required to know RFC2616 intimately. The HttpClient library
should do the right thing and use the network in the most efficient manner possible.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message