The first two sections in this lesson discussed all of the applet-specific API. However, most applets rely on a lot of API that isn't specific to applets. This section gives you hints about using the Java API, covering the areas that are affected by applets' close relationships with browsers.
This section lists the security restrictions that untrusted applets face. It also describes some ways to get around the restrictions.
This section discusses the elements of an applet's UI. It then goes on to give hints for creating a GUI and creating debugging output using the standard output and standard error streams.
This section discusses the system properties that an applet can get to find out about its environment. It includes an example applet that displays the ten properties applets can get. It also lists some properties that applets typically can't get.
This section delves into the issues of using threads in applets. A thread — sometimes called an execution context or a lightweight process — is a single sequential flow of control within a process. Even the simplest applets run in multiple threads, although it's not always apparent. Many applets create and use their own threads so that they perform well without affecting the performance of the browser they run in or the performance of other applets.
This section shows how even untrusted applets can use networking code to communicate with programs running on the host from which they came.