Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Thu, 24 Jul 2008 17:48:49 +0100
From: Nick Kew <nick@webthing.com>
To: modules-dev@httpd.apache.org
Subject: Re: porting from IIS
Message-ID: <20080724174849.79a333e3@grimnir>
In-Reply-To: 
 <5B0ECC1928CB6C479A734A6BD6209EF002D3FEB7@exchange.Giant-Steps.local>
References: 
 <5B0ECC1928CB6C479A734A6BD6209EF002C7D773@exchange.Giant-Steps.local>
	<20080703154934.2fc192e0@grimnir>
	<5B0ECC1928CB6C479A734A6BD6209EF002D3FEB7@exchange.Giant-Steps.local>
Organization: WebThing
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 24 Jul 2008 15:56:07 +0300
"Harold J. Ship" <Harold@giant-steps-networks.com> wrote:


> How it works today: there are 3 types of request: light, medium and
> heavy.
> We will need 2 "pools" of threads. One for handling light requests,
> and one for medium/heavy.

That sounds rather like a new MPM.

> The light requests can be dealt with by the usual mechanism.
> The medium and heavy requests should be passed by the to the other
> thread pool, freeing the original "ordinary" thread to handle more
> incoming requests.

That, on the other hand, sounds like solving a problem that
isn't there.  Unless you really need priority queues, you can
just let everything run in parallel.

> We are worried that if we try to process the medium and heavy requests
> with a thread pool, then either the "ordinary" thread will block
> anyway, or the next filter will get starved.

Hmm?  Why do you suppose that?

> The heavy requests mentioned above are to be sent to another server.

So that's a (reverse) proxy architecture.  Apache is happy with that,
and indeed it's a very common scenario.

-- 
Nick Kew

Application Development with Apache - the Apache Modules Book
http://www.apachetutor.org/