well the question was a bit off topic becoz i am not allowed to use a servlet :)) or a port either.
The applet class will be loaded on individual machines and the objects will be saved on the local hard disk. If u r further interested in knowing why the requirement is so !!! Well this is a backup application which will be used when the port is down. -----Original Message----- From: Michael Weller [mailto:[EMAIL PROTECTED]] Sent: 14 May 2002 12:18 To: [EMAIL PROTECTED] Subject: Re: persistent objects : a bit off topic hi! This won't work for sure: java.sql.Connection is an interface, so a class can't extend it :) A concrete implementation of Connection comes with your jdbc-driver (just like HttpSession is an interface which is implemented by the author of your servlet-container). Anyway: Where would you save the serializable Connection object so that another applet can use it? Can't you connect your applet to a servlet that passes serialized objects back to it after request or let your servlet talk XML with your applet. This way your servlet can keep a ConnectionPool to recycle Connection objects/create fewer connection objects, and your servlet can cache the data so that your database only needs to be accessed if the data changed. -mw ___________________________________________________________________________ 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
