On Mon, 2013-06-17 at 15:28 -0400, Jeff Segal wrote:
> I am trying to use URIBuilder to create a URI representing a request to an
> endpoint that supports duplicate parameters in the query string. In other
> words, a request might look like "http://example.com/service?foo=bar&foo=baz";.
> From my t
Thanks Oleg, looks like I missed that method.
On Tue, Jun 18, 2013 at 4:49 AM, Oleg Kalnichevski wrote:
> On Mon, 2013-06-17 at 15:28 -0400, Jeff Segal wrote:
> > I am trying to use URIBuilder to create a URI representing a request to
> an
> > endpoint that supports duplicate parameters in the
On 6 Jun 2013, at 8:56 PM, Oleg Kalnichevski wrote:
> On Thu, 2013-06-06 at 18:25 +0200, Sebastiano Vigna wrote:
> What's wrong with using an explicit HttpHost with a resolved address?
OK. We have implemented it that way (and thanks for adding the INetAddress
constructor) but we're still seein
On Tue, 2013-06-18 at 15:11 +0200, Sebastiano Vigna wrote:
> On 6 Jun 2013, at 8:56 PM, Oleg Kalnichevski wrote:
>
> > On Thu, 2013-06-06 at 18:25 +0200, Sebastiano Vigna wrote:
> > What's wrong with using an explicit HttpHost with a resolved address?
>
>
> OK. We have implemented it that way (
On 18 Jun 2013, at 3:20 PM, Oleg Kalnichevski wrote:
> Are you using plain HttpCore or HttpClient?
DefaultHttpClient, actually. We're moving soon to the new (non-deprecated)
classes.
Ciao,
seba
-
On Tue, 2013-06-18 at 15:23 +0200, Sebastiano Vigna wrote:
> On 18 Jun 2013, at 3:20 PM, Oleg Kalnichevski wrote:
>
> > Are you using plain HttpCore or HttpClient?
>
> DefaultHttpClient, actually. We're moving soon to the new (non-deprecated)
> classes.
>
> Ciao,
>
Could you please run your
Taking a look at async client 4.0-beta4 and looking for a little guidance.
With beta3 we had some code like:
PoolingClientAsyncConnectionManager asyncMgr = new
PoolingClientAsyncConnectionManager(new DefaultConnectingIOReactor());
asyncMgr.setMaxTotal(maxConnections);
On Tue, 2013-06-18 at 14:13 +, Matt Brown wrote:
> Taking a look at async client 4.0-beta4 and looking for a little guidance.
>
>
> With beta3 we had some code like:
>
> PoolingClientAsyncConnectionManager asyncMgr = new
> PoolingClientAsyncConnectionManager(new DefaultConnectingIOReactor()
Oh that's embarrassing - my start() had been inadvertently commented out.
Thanks!
-Original Message-
From: Oleg Kalnichevski [mailto:ol...@apache.org]
Sent: Tuesday, June 18, 2013 9:37 AM
To: HttpClient User Discussion
Subject: Re: Async beta4 Connection Pooling
On Tue, 2013-06-18 a