charlie hunt wrote:
> If a change in configuration shows a significant change in Grizzly's
> performance, then I think we have a bug, i.e. an "out of the box"
> configuration bug.
>
Right now the only way to configure grizzly properly is by properly
calling the SelectorThread.setXXX...since documentation is quite bad, it
is easy to forget to call one method and get bad results :-)
Documentation will helps a lot :-)
A+
-- Jeanfrancois
> charlie ...
>
> Jeanfrancois Arcand wrote:
>> http://weblogs.java.net/blog/forax/archive/2008/02/sorry_but_ive_t.html
>>
>> I would think he should post its configuration :-) But that's good
>> publicity for us anyway :-)
>>
>> 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
>>
>