Sergio Oliveira Junior wrote:
> If I cannont have a pool of keep-alive connections to do a descent chat
> server using servlets, than servlets sucks !!!
>
An analogous argument: "if I cannot carry a two-ton load of lumber in the back
of my Porsche, then Porshes suck!".
Moral of the story: use the right tools for the right job. Servlets are based
on the request/response nature of the HTTP protocol. This works great for many
(but not all) application domains. Doing a good chat application really
requires persistent connections so you can do "push" type messaging. HTTP was
not designed for that.
On the other hand, let's see you scale a chat application that depends on
persistent sessions up to the 10k-100k simultaneous user environment that many
high profile web applications have to support :-).
>
> OBS: I don't want to use SingleThreadModel. Otherwise performance will suck
> and I will have to work with static methods and variables or
> setAttribute/getAttribute.
>
> Does anybody think differently ?
>
SingleThreadModel does not help you or hurt you with respect to persistent
connections.
> SAOJ
>
Craig McClanahan
====================
See you at ApacheCon Europe <http://www.apachecon.com>!
Session VS01 (23-Oct 13h00-17h00): Sun Technical Briefing
Session T06 (24-Oct 14h00-15h00): Migrating Apache JServ
Applications to Tomcat
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
