- When building applets with the SmartSockets Java Class Library (and networking applets in general), keep in mind the security restrictions placed on applets, such as limited host connectivity and lookup and little or no local file access.
- When deploying SmartSockets applets with typical security restrictions, RTserver must be running on the same host as the web server for downloaded applets to connect back to.
- Applets can have very different life cycles from applications; care must be taken to ensure that your program will respond and survive "reloads" and other actions. Sun’s appletviewer is a very good tool for testing these cases.
- SmartSockets applets should utilize a messaging thread, spun off by your applet’s
start method. Performing a TipcSrv.mainLoop to ensure message delivery should be this thread’s sole responsibility.
- Not all Java Virtual Machines (JVMs) especially those in web browsers, necessarily behave identically. We recommend testing applets with Sun Microsystems JSDK and the appletviewer utility or with the HotJava browser.