Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #14878

Re: Chrome bug with Applet and threading

From "Richard Maher" <maher_rj@hotspamnotmail.com>
Newsgroups comp.lang.java.programmer, comp.lang.javascript
Subject Re: Chrome bug with Applet and threading
Date 2012-05-29 20:17 +0800
Organization HTTP *is* The Box - Let's think outside
Message-ID <jq2epo$jrt$1@speranza.aioe.org> (permalink)
References <jpmd6h$gvk$1@speranza.aioe.org> <XnsA05E5D966C1D2eejj99@194.109.133.133>

Cross-posted to 2 groups.

Show all headers | View raw


"Evertjan." <exjxw.hannivoort@interxnl.net> wrote in message 
news:XnsA05E5D966C1D2eejj99@194.109.133.133...
> Richard Maher wrote on 25 mei 2012 in comp.lang.javascript:
>> Please see Chrome bug report: -
>> http://code.google.com/p/chromium/issues/detail?id=129528
>>
>> If you can identify a bug in my code that is causing the hang on
>> Chrome them please let me know. Otherwise please vote for this issue
>> by ticking the star. SSCCE provided and behaviour very easy to
>> reproduce.
>
> Off topic, Java != Javascript.

Can you please explain why you are so adamant that all of the Javascript on 
the readily available: -
http://code.google.com/p/chromium/issues/attachmentText?id=129528&aid=1295280000000&name=hydra.html&token=uG9gNfEjUC8sTqGvGvrDTjpYD1E%3A1338292470931
is not responsible for the hang with the Chrome browser?

Perhaps the "dispatcher" method gets an exception and prevents the Applet 
callback from calling notifyAll()? But that would surely only block one TAB?

Regardless, my decision to alter the Javascript so that the user's 
"callback" JS function no longer has to call a "rendezvous" method but 
rather return a true/false indicating end-of-stream for a reply/result-set 
culminated in a solution that now works with every browser except Chrome. 
Maybe a further tweak to the Javascript/DOM could get Chrome to obey the 
rules? (Certainly appending the DIV child to the document.body *before* 
seting its <object> innerHTML got IE8 over the line with Applet activation!)

Anyway, underneath all this is a single Java thread multiplexing output to 
any number of TABs in a browser instance that constitute an Application, and 
I think a lot of people would find that very interesting! Having said that, 
to date, nobody could be bothered to tick a simple star so maybe no one 
cares?

>
>
> -- 
> Evertjan.
> The Netherlands.

Oh, I get it! It's just that you can't wait till August when you and your 
Cloggie mates get to take your caravans down to the autobahns and really 
give complete strangers the shits?

Regards Richard Maher

Back to comp.lang.java.programmer | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Chrome bug with Applet and threading "Richard Maher" <maher_rj@hotspamnotmail.com> - 2012-05-25 06:36 +0800
  Re: Chrome bug with Applet and threading "Evertjan." <exjxw.hannivoort@interxnl.net> - 2012-05-25 07:12 +0000
    Re: Chrome bug with Applet and threading "Richard Maher" <maher_rj@hotspamnotmail.com> - 2012-05-29 20:17 +0800
      Re: Chrome bug with Applet and threading Scott Sauyet <scott.sauyet@gmail.com> - 2012-05-29 06:15 -0700
        Re: Chrome bug with Applet and threading "Richard Maher" <maher_rj@hotspamnotmail.com> - 2012-06-03 08:59 +0800
      Re: Chrome bug with Applet and threading Lew <noone@lewscanon.com> - 2012-05-29 07:02 -0700

csiph-web