Network Station Java Programming

Last Update April 2, 1998
 
South Fork Software is aware of the subtleties of network station Java programming. Java applications run no differently on network stations than on PC's, but because the application class files are stored on a network server and because network stations are often less powerful than PC's, carefully tuned Java network performance is more important for network stations than PC's.  

Java enterprise applications consist of a large number of Java class files. Java class files are typically small files, about 2k to 25k bytes. Individual Java class files are loaded from storage to memory as they are needed to create objects. Class files remain in memory as long as (one or more) objects of that class are in use or as long as unused memory space exists. When unused memory space is low the Java garbage collector removes the least recently used class files from memory.

When the Java application is located on a network server, loading class files takes more time than loading class files from workstation local disk. Several things may be done to minimize and manage class loading time for network stations, and PC's running a server resident Java application.

Application speed on the network station Java virtual machine needs to maximized. This is a matter of efficient Java programming. String buffers are much faster than string manipulation. Careful application testing to avoid repeated connections and unnecessary loop cycles. Testing the actual run time of often used methods will focus application optimization.

South Fork Software would like to put this experience to work for you.
507 875 2428
72640.2025@compuserve.com
fpvw@sfsw.com

Mail to: South Fork Software