Hi Nic! & others!

   I'm planning to write a servlet which will act as a server. Many clients will be 
calling the servlet. So I was just thinking about the need for connection pooling( one 
connection handled by one thread seperately)
   Any links to Articles on Thread, specially which gives info about when it's good to 
use & not to use.
   Thing is that If I write a server, should I create a seperate thread for each 
client connected? If I do create seperate threads, If client No increases What could 
be the problems.

Thanx in advance.

Chinni




On Friday, September 08, 2000 at 07:42:42 AM, A mailing list for discussion about Sun 
Microsystems Java Servlet API Technology. wrote:

> >>> Chinni <[EMAIL PROTECTED]> 08-Sep-00 7:15:14 AM >>>
> >Can someone write about their experiences about
> >Servlet's performance.
> >MAy be things like:
> >1. What kind of problems faced AND how it was solved.
> >2. What are the areas need to take care while developing
> >3. Using Thread and its implications +ve & -ve.
>
> What is the title of the assignment you've been given?
>
>
> Nic
>
> ___________________________________________________________________________
> 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
>


--
mailmetoday is a free e-mail service from India Today Group Online that also rewards 
you with cool gifts. Sign up now at http://www.mailmetoday.com

___________________________________________________________________________
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

Reply via email to