quick question about applets
Jesus Arango
Can someone tell me the difference between an applet running in a browser
and a stand-alone java application? I'm particulary interested in those
things which you cannot do with applets.
I want to write an applet that keeps running even after the user has
dismissed the document in which the applet is embedded.
How can I do this?
Thanks
Jesus Arango
Jim Piersol
Jesus Arango wrote in message <7a2a5r$e58$1...@msunews.cl.msu.edu>...
Roedy Green
<jar...@mymail.com> wrote:
>I'm particulary interested in those
>things which you cannot do with applets.
See "Applet", "sandbox" and "security" in the Java glossary.
Quoting from the Applet section of the Java glossary:
An applet is a partial Java application program designed to run inside
the womb of a WEB browser, with help from some predefined support
classes. To make them very safe to run, even when they were composed
by teens with the morals or skill of Beavis and Butthead, Applets are
severly restricted:
1. They are not allowed to print.
2. They are not allowed to write to serial ports.
3. Applets are not permitted to read or write files. They are not even
allowed to look in a directory or test for the existence of a file.
There is loophole, if you have the user's co-operation.
4. No talking to strangers. Applets may only communicate with the
server they were spawned from. If they were loaded from a local disk,
they can't talk to any webserver. They could send/receive email
to/from a different host, but only via the home host. Signed Applets
can bypass this restriction by doing a
PrivilegeManager.enablePrivilege("UniversalConnect"); to turn on the
ability to talk to any host.
5. No calling native methods.
6. No spawning external programs.
For the JAVA GLOSSARY and the CMP Utilities: <http://mindprod.com>
--
Roedy Green, Canadian Mind Products
-30-