Return-Path: Delivered-To: apmail-hc-dev-archive@www.apache.org Received: (qmail 33356 invoked from network); 31 Jul 2009 16:00:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 31 Jul 2009 16:00:37 -0000 Received: (qmail 81120 invoked by uid 500); 31 Jul 2009 16:00:38 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 81056 invoked by uid 500); 31 Jul 2009 16:00:38 -0000 Mailing-List: contact dev-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list dev@hc.apache.org Received: (qmail 81046 invoked by uid 99); 31 Jul 2009 16:00:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Jul 2009 16:00:38 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Jul 2009 16:00:36 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 98C95234C046 for ; Fri, 31 Jul 2009 09:00:15 -0700 (PDT) Message-ID: <1806846353.1249056015621.JavaMail.jira@brutus> Date: Fri, 31 Jul 2009 09:00:15 -0700 (PDT) From: "Oleg Kalnichevski (JIRA)" 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HTTPCLIENT-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737575#action_12737575 ] Oleg Kalnichevski commented on HTTPCLIENT-834: ---------------------------------------------- Welcome back, James. Not much has changed since I committed your patch. The code is still in the 4.1 branch (to be merged down to trunk after 4.0 GA release) [1]. I am still of the same opinion that DefaultHttpClient ought not have the transparent content coding enabled per default (there are different options of solving the problem, HTTPCLIENT-838 being one). You should still consider submitting an an individual or a corporate CLA. All discussions about HttpCore / HttpClient development should take place on the dev mailing list. Oleg [1] http://svn.apache.org/repos/asf/httpcomponents/httpclient/branches/branch_4_1/ > 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 > > > 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