Hi!
> Sounds like you're not going to like servlets and JSP pages very much :-).
>
> One of the key issues you might not have considered is that servlets and
> JSP pages operate in a multithreaded environment. One of the things that
> means is that, if two users submit requests for the same servlet at the
> same time, those requests will run simultaneously. If you were using
> instance variables in the servlet to store them, the two users are going
> to stomp on each other.
>
> To avoid this problem, you need to store things related to a particular
> request or user in separate objects. That's what the beans do for you --
> and that's why you should learn to use them even if you don't currently
> feel comfortable with them.
>
> One source of information on good practices in designing large web-based
> applications is the Java2 Enterprise Edition (J2EE) "Best Current
> Practices" manual on web application design. The chapters on servlets and
> JSP are very useful, even if you don't need a full blown application
> server.
>
> You can get this document by going to <http://java.sun.com/j2ee> and
> following the links for documentation downloads.
Maybe this sounds a bit strange but is it possible to interact with a
servlet from a bean called by a jsp file? The main pro for servlets I have
on my side is a) its lifecycle and b) its possibilities to save/maintain
informations. As soon as I decide to use JavaBeans I could also have used
php4 or another scripting language.
My Idea behind the whole project is to have on multithreaded application
that retrieves and handles all data. This "application" would be perfectly
represented with a "servlet". This backend application should deal with
db-pooling, connection handling (HTTP, TELNET!, ...) and NOT with any
user.output. I first want to pass any Data back to the client when all data
was processed.
I first wanted to build a simple backend application that does all the stuff
I mentioned. I would then have used a servlet to handle user request and to
pass the data to my application using RMI. What I don't like about this is
the traffic that travels over my network and the thing with threading.
Handling User Request and Databases in one application seemed to be done
quite nice by servlets.
IS a Bean able to use RMI in an acceptable way, or are there any other ways
to share informations between Java
Application without writing a whole raw-socket-type protocol?
Thanks,
Thomas
___________________________________________________________________________
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
