Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Received-SPF: pass (nike.apache.org: domain of bill.speirs@gmail.com
 designates 209.85.216.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1314365389.4578.39.camel@ubuntu>
References: 
 <CAB_f4-Um_rgp+4EkZMBL2_pp7TmT-_w8ensiPUCKHQ7MuOiurQ@mail.gmail.com>
	<1314196752.1969.92.camel@ubuntu>
	<CAB_f4-XgbXOM8naXbh5pEEb1eSCfBsNCt9YMsSP59BSu3TchDQ@mail.gmail.com>
	<CAB_f4-U_2CPAgGDFnKAa24_F+PjORqhnabj3jeJUtdvYrtHr+Q@mail.gmail.com>
	<1314365389.4578.39.camel@ubuntu>
Date: Fri, 26 Aug 2011 11:09:27 -0400
Message-ID: 
 <CAB_f4-W3z1DWCPuFR-C2z7Ei3THTaMhNBFW8B1Ahz2MUQeiCYw@mail.gmail.com>
Subject: Re: HttpParams appear to be static/global
From: Bill Speirs <bill.speirs@gmail.com>
To: HttpComponents Project <dev@hc.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

This is very much the type of thing I'm looking for. What I do not
understand how to accomplish is having one (or a few) threads which
handle the i/o events for both the incoming requests and the outgoing
requests to the back-end services, and then their responses.

I'll take a look at the source for Apache Synapse though...

Thanks!

Bill-

On Fri, Aug 26, 2011 at 9:29 AM, Oleg Kalnichevski <olegk@apache.org> wrote:
> Bill,
>
> A very common pattern for proxies (used by Apache Synapse, for instance)
> is to have a small number of i/o dispatch threads (approx. as many as
> the CPU cores) handling i/o events for incoming and outgoing connections
> asynchronously and a larger pool of worker threads that are employed to
> execute long, potentially blocking operations (such as content
> transformation). I _suspect_ that is what you want.
>
> Oleg
>
>
>
> ---------------------------------------------------------------------
> 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