I'm wondering what the best approach would be to instantiate and access a singleton object from a servlet where the object runs in its own process (i.e. not in the application scope of the servlet), so that it is not affected by the servlet's life cycle and does not affect the servlet. I considered a standalone RMI object being accessed from the servlet, but I'm concerned that the network serialization overhead would be prohibitive given the size of the object (basically a very large array). But can avoid networking if I want this object to run in a separate Java process from my servlet engine? EJBs are not applicable to the problem. Thanks, Dan -- Daniel Kirkdorffer Redmond Office: 425-376-0505 x241 Sr. Consultant, WebVision Email: [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
