Lets say that such a feature exists - you do realize that you will NOT be able to access it via the applet correct? It would need to be configured via some other process.
thanks for your reply. What we are able to see is that when you close the applet (i.e. simply leaving the page where the applet is running) if you are able to access again the applet within the next minute then the same java.exe process is used. This is just what we need as that process has been already authenticated against our web server while if a new process is started then this has to be authenticated again.
Processes are not authenticated against web servers as such. What I understand is that there is some info that the first process has, due to authentication, that has to be passed to the web server and is not available anymore in the second process. Couldn't you persist this info somewhere and pick it up again in the second process? By the way, is the applet signed?