Comments on: Using Applets to Play Outside of the Sandbox

By: usdubxllc

usdubxllc — Sat, 21 Oct 2006 16:24:12 +0000

bggmoqcak

tluoqbzblo ykgaujhdxi gdzmxmisa dglptfxldc

By: Zhou Renjian

Zhou Renjian — Tue, 17 Oct 2006 16:27:19 +0000

I met the same thing about 2 years ago. And many of my JavaScript calls are restricted so the calls need to be asynchronized. But my JavaScript calls just should be a syncrhronous call. So callbacks are used, and the Applet is now became a server! And JavaScript became a browser! Both are in asynchronous mode! What about there are two restricted calls should work together with a middle JavaScript DOM action and before/after actions? You must block and indicate the user in JavaScript side. Lots of other problems came to me contributing paints at that time.

I just remember that nightmare of integrating Java Applet and JavaScript together. So I recommend you NOT to rush to such “JavaScript in Applets – Getting Out of the Sandbox technology” until you are ready for nightmares. Actually I recommend NO Java Applet + JavaScript.

By: Julien Couvreur

Julien Couvreur — Tue, 17 Oct 2006 15:46:36 +0000

MashProxy is another Java based solution to extend the browser, but with cross-domain capabilities: http://mashproxy.com/
The problem with Java is that once you manage to pry the door open, things quickly become dangerous. It’s hard to achieve a controlled amount of openess and it’s easy to create additional security risks.

By: JacSoyYo

JacSoyYo — Tue, 17 Oct 2006 15:04:23 +0000

I had same problem several months ago trying to print barcode labels from a web application and that was the only way to avoid the security warning everytime, I found it on Sun forums (had to dig a lot tho).

By: Thomas Messier

Thomas Messier — Tue, 17 Oct 2006 15:03:48 +0000

I’m gonna bookmark this page just in case! I remember doing some stuff with signed applets a couple years back, an absolute nightmare…