Posted by nheger
on July 21, 2009 at 11:19 PM PDT
We have 4 Applets on one page which communicate with each other.
I thought it would be a good idea to make the max. memory size for one of them bigger using the new java_arguments applet tag to set the max size to 128M.
That works fine, but now I noticed I have 2 JVMs running (previously: 1), and Applet #1 (unsigned) can't talk to #2 (signed) anymore. I don't know if signed/unsigned has any significance here.
I understand that specifying a -XMX memory size will create a new JVM "if none can be found", and on the same page it's explained that "there is no way to guarantee that an Applet will be started in one JVM and not in another". Great.
That leads me to several questions:
- Why do the Applets not talk to each other anymore? Is it because one is unsigned, and the other one is signed? Is it because they run in different JVMs? They can talk to each other just fine if they all run in the same JVM.
- Is there a way to actually have the applets all start in the same JVM? It seems like I could specify the same memory size for all of them and hope for the best - but the instructions say there's no guarantee so I am afraid a later plug-in update will break it.
- Can I move completely to JNLP definitions and solve this problem there? Are there special allowances or parameters I can set in JNLP to allow Applet-Applet communications?
- Do Applets running in different JVMs simply not talk to each other even if they are on the same web page?
Thanks for any insights. The topic of Applet-Applet communication seems to be completely left out of the new plug-in documentation... unless I just didn't see it, if so please post links. Thanks!