[
https://issues.apache.org/jira/browse/HTTPCLIENT-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682318#action_12682318
]
Oleg Kalnichevski commented on HTTPCLIENT-834:
----------------------------------------------
Hi James
(1) ThreadLocals are often considered evil and ought to be avoided, especially
in general purpose libraries. If you need to persist some data between
different interceptors please consider using HttpContext. This is precisely
what it is meant for.
(2) Please consider providing some means of defining applicable content coding
algorithms and their order of preference.
(3) Patch utility compatible diff would be nice.
Oleg
> 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 3
> Environment: Any
> Reporter: James Abley
> Attachments: 834.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-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
