Yes, u are right. In the context of servlets, a particular user may trigger the same servlet many times thus sharing his own session object. U explained this nicely in ur other mail. --Mukul Gandhi At 09:51 AM 7/7/99 -0500, you wrote: >Actually, what is created in your example is a local reference to a shared >object. The real question is can one of my objects be modified by some >external force. That external force could be many things one of which is >another thread of execution in this program. If you reference objects that >have external representation (database, file, shared memory, network, etc) >they all can be changed by external forces. Thus care must be taken to >either: >1) Handle all possible changed in the code that references the objects.. >2) Handle all possible changes in the objects themselves.. >3) Some middle ground, where that middle ground is well documented and >understood by both the object implementor and the object user.. > >The debate that constantly rages is which of the three mechanisms above is >"best". And the answer is.....depends upon your needs! > ___________________________________________________________________________ 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
