>>> Dave Brosius <[EMAIL PROTECTED]> 05/03/01 14:25:33 >>>
>If my servlet must perform some external
>process, rmi, sockets, etc. I monopolize the
>Servlet thread until my process is done, for
>no good reason. If n jobs are waiting for the
>external process to complete, NO THREADS
>are available from the Servlet Container pool,
>and all http-servlet traffic halts.
Not so. All the thread pools I've seen (including GNU-SocketServer
which I wrote) are able to create more threads for the pool as the
pool runs out of threads.
Extra threads are discarded when the server returns to normal thread
availability.
Thus your syncrhonicity problem never appears. There has been a lot
of discussion of this on the archives. Also there are several free
servlet engines that you could look at to see how they avoid these
synchronicity problems.
You'd be welcome to join the GNU-Paperclips mailing list where I (or
one of the others there) would be happy to explain how Paperclips
works.
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
