Making a socket server connection from java applet
in [Java Help]
|
From: Knute Johnson on 11 Sep 2009 12:18 Richard Maher wrote: > Hi Knute, > > "Knute Johnson" <nospam(a)rabbitbrush.frazmtn.com> wrote in message > news:4aa9c4da$0$19419$b9f67a60(a)news.newsdemon.com... >> Richard Maher wrote: >>>> I worked on a project a few months ago that >>>> used applets to communicate with a server program running at the >>>> applet's host. I do know that you must use the new plugin which is > only >>>> available in later versions of 1.6 >>> I don't agree. (At least in a general sense without know your specific >>> project requirements) >>> >>> The example code I pointed to quite happily closes the Socket when you >>> navigate away from the page and then back again. If you don't believe me >>> try: - >> Richard, I just curious, what part don't you agree with? The part about >> using the new plugin or that it is only available with the newer 1.6? > > The part where you say "I do know that you *must* use the new plugin". The > Tier3.jar file that the example uses was built with 1.4.2_13 and has no > trouble at all without the new plugin. (And also performs very well with the > new plugin) If you were refering to better or more predictable support for > stop/start methods with the new plugin then I'm happy to hear about it, but > for the OP's case I think it could be beneficial to change to init/destroy > if moving off/on a page is what he's looking at. > > Cheers Richard Maher Prior to the new plugin any running threads could just be destroyed without finishing including the one running stop() and destroy(). This makes cleanup very difficult and is most likely (in my opinion) the cause of the OPs problem. -- Knute Johnson email s/nospam/knute2009/ -- Posted via NewsDemon.com - Premium Uncensored Newsgroup Service ------->>>>>>http://www.NewsDemon.com<<<<<<------ Unlimited Access, Anonymous Accounts, Uncensored Broadband Access
From: EJP on 13 Sep 2009 02:01
mikek wrote: > What I meant > by non-bindable is that this is the error message in the java console > when the applet tries to open the server connection after, for > example, navigating away from the page and then returning to it. So why does the applet try to open the 'server connection' *again?* If the applet has been unloaded and has destroyed itself correctly it should have closed the ServerSocket so it should be able to open a new on when it is initialized. If it hasn't been destroyed it should still have a reference to the existing ServerSocket. BTW this is not a 'connection', it is a ServerSocket, which is a passive listening endpoint. |