Communicating with Other Programs

Using a Server to Work Around Security Restrictions

As the Understanding Applet Capabilities and Restrictions trail explains, applets are subject to many security restrictions. For example, they can't perform file I/O, they can't make network connections except to their original host, and they can't start programs.

One way of working around these restrictions is to use a server application that executes on the applet's host. The server won't be able to get around every applet restriction, but it can make more things possible. For example, a server probably can't save files on the host the applet's running on, but it'll be able to save files on the host the applet originated from.

This page features an example of a server that allows two applets to communicate with each other. The applets don't have to be running on the same page, in the same browser, or on the same computer. As long as the applets originate from the same computer, they can communicate through the server that's running on that originating computer. The example uses sockets, which are documented in All About Sockets.

Here are the source files:

TalkClientApplet.java

The source file for the client applets. (Both applets use the same source code.) After you compile it, you can run it by including it in an HTML page with this tag:

<applet code=TalkClientApplet.class width=550 height=200>
</applet>

Here's a link to a page that includes the above HTML code. After saving this page to a file on your local HTTP server, you can use it to communicate with the talk server

TalkServer.java and TalkServerThread.java

The source files for the server. After compiling both files, you can run the server on the applets' originating host by invoking the interpreter on the TalkServer class.

Here's a picture of the server in action:

Here are pictures of the applets in action:

Communicating with Other Programs