On 1/28/2012 5:01 PM, Pid wrote:
On 28/01/2012 09:07, bxqdev wrote:
<snip>
I see. Did you identify where the bottleneck was?
well, we are getting too far from the subject.
can you make up 3 cases when to use 3 combinations of
connector+servlet api
1. bio connector + async servlet
2. nio connector + sync servlet
3. nio connector + async servlet
i mean in which theoretical case each combination of connector+servlet
api is the best choice?
Nope.
it's not that hard, when you know the subject, but i guess,
unfortunately, it's not the case :)
Oh, that's even more crude than my baiting. Aside from which Mark
already gave a reasonable answer.
well, nothing personal. but if you can't explain - you don't know by
yourself. that's the rule :)
Still baiting, still not biting.
I might refer to your own replies, in which you made certain claims
without explaining how.
you're trying to change the subject, the point is: you don't know enough to
answer the original question.
3. How do i choose which one to use in any particular case?
First, don't prematurely optimise. Have you tested your
application
yet?
yes, i need a better throughput and performance.
Please provide details.
<snip>
yes, we're going to opensource it soon. stay tuned.
I shall.
what garbage collector do you use?
Depends.
ok. can you enumerate them though? are you able to give detailed and
comprehensive
answers, besides yeps, nopes and depends?
Yep.
unfortunately you've just proved the opposite :)
p
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
