[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] Thread pooling
- From: ronen hamias <ronen.hamias@xxxxxxxxx>
- Date: Mon, 4 Apr 2011 14:01:10 +0300
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=HmzNMhCQL099xnSuDmC0QhW7V99/kYtN3mmtuXI6Bsc3YdAZHwjjYEwRY046Yq0X6e v+TPYbroZPJuOd34N5JIR11a0kQRlFjdsLDaXcNAGbe3EWRCExh0CagvpvhdLKdXs+5A QpEzN0J4Rn1+mNBj8spPp4T133c7HqI0M3Z1k=
where should i report this bug?
On Sun, Apr 3, 2011 at 7:23 PM, Scott Lewis <slewis@xxxxxxxxxxxxx>
On 4/3/2011 9:07 AM, Ronen.hamias wrote:
Why the client side uses thread at
all at sync call why not letting the caller decide what thread
pooling by not supporting thread pooling from the consumer
side the caller can wrap the invocation with a runnable and
use thread polling of his choose ?
Just a thought...
Hi Ronen. It's a reasonable thought...although there are some
excellent reasons to have built-in support for asynchronous
invocation...and ECF has such support...see .
But if you wish to generalize things to support either a
single-threaded or multi-threaded use case (and this is easily done
through the use of IExecutor impls other than
ThreadsExecutor)...then please open bug, and contribute the
ECF is a community-supported project...so if you get something out
of it...please reciprocate by supporting and contributing to it.
ecf-dev mailing list