Salut,
Oleksiy Stashok wrote:
> Hi,
>
> basically we will not use Executors directly,
> but Grizzly new ThreadPool interface will extends ExecutorService.
I think we should let peoples drop their Executors in 1.9.0...the only
restriction we should impose is the ThreadFactory, which needs to create
WorkerThreads.
What do you think?
-- Jeanfrancois
>
> So it will be possible to use Grizzly's ThreadPool as general Executor.
>
> WBR,
> Alexey.
>
> On Nov 27, 2008, at 16:01 , Jeanfrancois Arcand wrote:
>
>> Hi,
>>
>> Alexey and I thinks that it might be time to drop the Pipeline
>> interface and directly expose Executors. In order to do that, we will
>> break backward compatibility with 1.8.x for application that were
>> using this interface. I do suspect we will not break a lot of
>> application, but just to make sure, I would like to propose the
>> following:
>>
>> (1) Assuming we don't see any performance regression (I've never
>> trusted the Concurrent's thread pool and demonstrated many time our
>> was faster), we switch to Executors
>>
>> (2) If a critical bug is found with 1.8.x users, we continue
>> maintaining the 1.8.x branch so peoples doesn't have to change anything
>>
>> Alexey has a patch that I will try and test to make sure no
>> performance regressions occurs.
>>
>> What peoples think?
>>
>> A+
>>
>> -- Jeanfrancois
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>