Return-Path: X-Original-To: apmail-hc-dev-archive@www.apache.org Delivered-To: apmail-hc-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7F84EFDC1 for ; Mon, 8 Apr 2013 11:07:54 +0000 (UTC) Received: (qmail 22649 invoked by uid 500); 8 Apr 2013 11:07:54 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 22595 invoked by uid 500); 8 Apr 2013 11:07:53 -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 22543 invoked by uid 99); 8 Apr 2013 11:07:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Apr 2013 11:07:51 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [217.150.250.48] (HELO kalnich.nine.ch) (217.150.250.48) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Apr 2013 11:07:44 +0000 Received: from [192.168.1.121] (77-57-197-206.dclient.hispeed.ch [77.57.197.206]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by kalnich.nine.ch (Postfix) with ESMTPSA id 9A25AB80124 for ; Mon, 8 Apr 2013 13:07:23 +0200 (CEST) Message-ID: <1365419242.2024.7.camel@ubuntu> Subject: Re: Following up HTTPCLIENT-1238 From: Oleg Kalnichevski To: HttpComponents Project Date: Mon, 08 Apr 2013 13:07:22 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.2-0ubuntu0.1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Mon, 2013-04-08 at 09:22 +0200, Simone Tripodi wrote: > Hi all mates, > > I am trying to support my colleague Dominique, the original HTTPCLIENT-1238 > reporter, on providing the patch to provide such OSGi feature. > > What we would like to achieve is registering proxy configuration(s) that > will be automatically picked-up by HttpClient instances, so users don't > have to manually register the proxy for each instance. > > In the issue I read that Oleg was working on APIs design in order to > achieve, more or less, the same goal, but after one day of investigation I > haven't figured out how to do it - may I can kindly ask you if there is any > way to implement that feature with current APIs, without adding additional > code? > > Many thanks in advance, all the best! > -Simo > Hi Simone Please have a look at the HttpClientBuilder and HttpClients classes in the 4.3 branch (trunk). What I think might be a feasible approach is to provide OSGi aware versions of those classes (similar to the caching module). OSGi aware builder can selectively inject OSGi specific dependencies instead of default ones or use a different CloseableHttpCllient implementation altogether. Hope this helps Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org For additional commands, e-mail: dev-help@hc.apache.org