Prev: Calling external program in java code
Next: JDK 1.5.0_21 released
From: Knute Johnson on 10 Sep 2009 16:15
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. The
> problem is that when navigating away from the page and then returning,
> the applet thinks the connection is closed but the browser must be
> keeping it open.

Most likely what is happening is that the socket is not getting closed
when you navigate away. 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 can't remember exactly which).
The reason for this is that stop() and destroy() may not get called in
earlier versions when the browser leaves the page. Also there may be
problems with certain browser versions too.

--

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: Richard Maher on 10 Sep 2009 18:29
Hi,

"Knute Johnson" <nospam(a)rabbitbrush.frazmtn.com> wrote in message
news:4aa95e5d$0$17243$b9f67a60(a)news.newsdemon.com...
> 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.

Which browser? Could be worthwhile ruling out BACK button optimization by
sticking an "onunload" function on your web-page.

>> The
> > problem is that when navigating away from the page and then returning,
> > the applet thinks the connection is closed but the browser must be
> > keeping it open.
>
> Most likely what is happening is that the socket is not getting closed
> when you navigate away.

I agree.

> 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: -

http://manson.vistech.net/t3$examples/demo_client_web.html

Username: TIER3_DEMO
Password: QUEUE

> (I can't remember exactly which).
> The reason for this is that stop() and destroy() may not get called in
> earlier versions when the browser leaves the page. Also there may be
> problems with certain browser versions too.
>
> --
>
> Knute Johnson
> email s/nospam/knute2009/

Cheers Richard Maher
>


From: Knute Johnson on 10 Sep 2009 23:32
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?

Thanks,

--

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: Richard Maher on 11 Sep 2009 05:21
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.
>
> Thanks,
>
> --
>
> Knute Johnson
> email s/nospam/knute2009/

Cheers Richard Maher
>


From: jolz on 11 Sep 2009 11:31
Did you set SO_REUSEADDR ?
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Calling external program in java code
Next: JDK 1.5.0_21 released