Client Side

On the client (i.e., web browser) side, an engine runs in its own thread, and takes care of receiving and processing data objects from its corresponding manager on the server through remote method calls to its advocate on the server side. Both the engine and the data have associated GUI objects which can be used for user interface. Data objects are generally polymorphic and know how to process themselves. The engine and the GUIs are all contained in a chassis object, which can be an applet or application.

A worker client, for example, could be an applet chassis containing a work engine which takes care of getting work data from the work manager, processing it, and requesting more work when it's done. To process the work, the work engine passes the work data pointers to itself and the work GUI, and then calls the work data's process() method. The work data then computes itself, using the work engine to communicate with the work manager, and the work GUI to report its progress status to the the user.