I got a web application that allows user to execute many menu items
which generate HTML pages back to the screen. Each interaction is a
full request/response cycle to a backend Java tomcat server.
We understand the security requirements of applets. We have a servlet
that is able to interact with the applet passing HTTP serialized objects
back and forth. All that works fine until the page is refreshed and the
applet is destroyed.
Does anyone have experience/best practices of what works best to keep a
single applet alive for the duration of a web user session? I'm
thinking we could do a popup window where the applet lives to keep it
alive. Any other advice or experience?
Thanks, Paul Holm
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.