Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <1330510570.6188.15.camel@ubuntu>
Subject: Re: HttpCore 4.1.4 and pipelined client
From: Oleg Kalnichevski <olegk@apache.org>
To: HttpComponents Project <dev@hc.apache.org>
Date: Wed, 29 Feb 2012 11:16:10 +0100
In-Reply-To: <4F4D4B97.1070602@optrak.com>
References: <4F4CB15D.3050707@optrak.com> <1330432272.6188.5.camel@ubuntu>
	 <4F4CDA6F.3040207@optrak.com> <1330440434.6188.13.camel@ubuntu>
	 <CAB_f4-XQ4LXbE4Oh3XUOHFMBuVWEpC-Vb=3D+3nOgQ00t0Bzww@mail.gmail.com>
	 <4F4D4B97.1070602@optrak.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0

On Tue, 2012-02-28 at 21:48 +0000, Mark Thornton wrote:
> On 28/02/12 21:07, William Speirs wrote:
> > Mark-
> >
> > Have you looked at SPDY? It handles the "multiplexing" that you're looking
> > for with respect to out-of-order requests.
> >
> > I started to try and implement SPDY inside of HttpComponents, but didn't
> > get super far (that probably lacks my latest changes):
> > https://github.com/wspeirs/SPDYComponents
> >
> > If you'd be interested in working on such a thing, let me know.
> >
> > Bill-
> I haven't looked at it yet. I am hopeful of getting the pipelining 
> working sometime tomorrow. Doing a replacement for 
> AsyncNHttpServiceHandler at the moment. In this case it seems straight 
> forward to support both pipelining and CONTINUE, at least with my 
> interpretation of the rfc. That should suffice to get my code working.
> 
> Our reason for using http in the first place was the ease of using a 
> browser for testing. While it doesn't test the pipelining it does make 
> it easy to very the basic results. I will have a look at SPDY once my 
> immediate task is complete.
> 
> By the way, is anyone interested in seeing my handlers with (in order) 
> pipeline support?
> 

Mark

You are also welcome to contribute such implementation to the project,
but ideally in this case it should be consistent with the 4.2 API

Cheers

Oleg

> Thanks for your interest
> 
> Mark
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org