Dave Brosius <[EMAIL PROTECTED]> wrote:
>
> 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.
>
> Sorry, but synchronous servlets are a hugh limitation. Obviously my example
> was very simplicistic.
"Simplicistic" :) or not, by no means whatever you do with that thread
implies that the whole HTTP traffic is blocked... Actually, you should be
still able to process other requests while your is waiting for the external
processes to terminate...
I would like to understand what you're trying to do "in toto", because I'm
sure that it's a problem that can be easily solved with the current API...
Pier
--
----------------------------------------------------------------------------
Pier Fumagalli - Sun Microsystems Inc. - <mailto:[EMAIL PROTECTED]>
___________________________________________________________________________
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
