i'm setting off to build a servlet project, and a (well, many) question
arises: since servlets are instantiated but once by the servlet
execution engine, the "conventional wisdom" (which i so far by into) is
to avoid instance variables and keep variables local to methods.
assuming that one's project can be done in this way, have there been
occurrences of the stack blowing?? i understand that it is a virtual
stack in the virtual machine, but since method variables are allocated
on this "stack", i am concerned that an architectural decision taken
early on could come back to bite one in a tender spot. i've checked the
java web site, but couldn't come up with any entries regarding stack
behavior; with servlets or otherwise.
thanx,
robert young
oms, inc.
___________________________________________________________________________
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
