Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Message-ID: <40DD863E.1050103@gmx.de>
Date: Sat, 26 Jun 2004 16:20:46 +0200
From: Joerg Heinicke <joerg.heinicke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.7) Gecko/20040616
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: Can I queue http requests in Cocoon 2.1.5 standalone?
References: <40D977E3.2010509@c.dk>
In-Reply-To: <40D977E3.2010509@c.dk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

On 23.06.2004 14:30, Thorbj�rn Ravn Andersen wrote:

> I have a situation where I want to use vanilla Cocoon  with a few extra 
> classes to render XSL-FO to an untraditional format, which I have 
> working with the Jetty included.
> 
> What I need to do now, is to limit the number of concurrent requests to 
> avoid FOP to run out of memory, since we may have quite demanding prints 
> and being able to isolate it is the primary reason for this exercise.  I 
> thought that the Avalon pool parameters were for this, but that is 
> apparently for determining when to destroy or pool components.
> 
> So, what I need is a way to say "If there is already X requests running 
> when the next http-request happens, then wait until one of the active 
> jobs finish and then execute the waiting job" and allow quite a queue to 
> build up. Can this be done with what is included in Cocoon?


Sounds like a task for the servlet container. If it is not configurable, 
you can reach that functionality probably by using servlet filters.

Joerg

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org