The applet below is connected to Lisp where all the work is done. Lisp calls Java to make the applet GUI components, but the database is maintained in Lisp.
The applet above is connected to Lisp where all the work is done. Lisp calls Java to make the applet GUI components, but the database is maintained in Lisp. The Lisp code is running in the remote server. The Java applet code is running in the browser plugin.
As the mouse moves around the window, the status area at the bottom edge is updated by local Java code. Button presses are sent back to Lisp for handling there, hence the greater delay.