Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Message-ID: <1778032123.1249568354807.JavaMail.jira@brutus>
Date: Thu, 6 Aug 2009 07:19:14 -0700 (PDT)
From: "Oleg Kalnichevski (JIRA)" <jira@apache.org>
To: dev@hc.apache.org
Subject: [jira] Commented: (HTTPCLIENT-834) Transparent Content Coding
 support
In-Reply-To: <1272589212.1237151811067.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HTTPCLIENT-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740078#action_12740078 ] 

Oleg Kalnichevski commented on HTTPCLIENT-834:
----------------------------------------------

> I hopefully described in the ticket why I think that this should work out of the box without requiring changes for existing clients. 
> That's why I'm trying to get it working as part of the existing API. 

Yes, you did, but I still think the chance of breaking existing apps in some subtle ways is simply too high to have this feature enabled per default. 

> Would people need to alter their code (or maybe just Spring / Guice / etc configuration)?

Those who use a DI framework to wire together their components this would be a one liner config change.

> Should that be based on trunk or the existing 4.1 branch? 

4.1 branch. 

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 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