2009/12/17 Oleksiy Stashok <Oleksiy.Stashok_at_sun.com>
> We could provide a single point of entry for threadpools , so we can hide
>>> our mess.
>>> The mess could be brought down to 2 or so pool impls too.
>>>
>>> A static create method that returns whats optimal impl depending on the
>>> provided configuration.
>>> If statistical fluff is needed we return a slow version that gives that
>>> etc.
>>>
>>> Whats your opinion regarding this matter ?:
>>>
>> Just to make sure, you mean something like:
>> public static ExecutorService ThreadPool.create() {...}
>> public static ExecutorService ThreadPool.create(ThreadPoolConfig config)
>> {...}
>>
>> And for statistical pool, how do you want that exposed ?
>
> Well, the same way via ThreadPoolConfig.
>
> then people must class cast the returned value, thats pretty error phrone ,
how is that better then current situation ?.
> WBR,
> Alexey.
>
>
>
>> ?
>>
>> WBR,
>> Alexey.
>>
>>
>>> --
>>> regards
>>> gustav trede
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>
>>
>
>
> --
> regards
> gustav trede
>
>
>
>
--
regards
gustav trede