> Thanks for following it. Now I hope you got that question correctly.
> Why because The applet should not disturbed other application in the
> opened in the saem browser or other browser.
>> Thanks for following it. Now I hope you got that question correctly.
>> Why because The applet should not disturbed other application in the
[quoted text clipped - 7 lines]
> I'm afraid I wouldn't know, but there's bound to be someone around who
> does.
Ravi, you could try an experiment. Put two applets on the same page
which use the same static variable. If a change in the static variable of
one applet affects the second applet, then you know that they are sharing
JVMs. If not, then you don't know (maybe they're not sharing, or maybe
they're sharing, but the JVM is being sneaky and detecting what you're
trying to do and circumventing it).
- Oliver
Chris Uppal - 30 Mar 2006 17:07 GMT
> Ravi, you could try an experiment. Put two applets on the same page
> which use the same static variable. If a change in the static variable of
> one applet affects the second applet, then you know that they are sharing
> JVMs. If not, then you don't know (maybe they're not sharing, or maybe
> they're sharing, but the JVM is being sneaky and detecting what you're
> trying to do and circumventing it).
If they do change together then you know they are sharing classloaders within
the same JVM. If they do not change together then you know that either that
browser is not using a Sun JVM (or something derived from it), or that they are
sharing a JVM but using different classloaders for each applet. The Sun JVMs
do not allow more than one JVM to be created in the same process.
At least that's the case for JSE, what happens on phones, and so on, with
not-necessarily Sun JVM implementations, is anybody's guess.
-- chris