<zvika> > A servlet's instance does not get serialized between requests or at any > other time; therefore, there is no need for a servlet to implement the > Serializable interface at any case. </zvika>
There might exist an interesting case, in a clustered environment, where you might want the servlet itself to be mobile within the environment (provided, of course, that your client facade knows how to track it). In such a scenario, I feel, a Serializable Servlet might indeed be very useful. It would then be possible to change the servlet host dynamically, guided by whatever load computation algorithm, as might be. regards Pramod Nair ___________________________________________________________________________ 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
