The cajo grail SDK is used for transparent distributed computing between remote Java Virtual Machines, providing client user interfaces via Applets and WebStart. Through the cajo grail mechanism, services can dynamically discover and use each other, by specified functionality. Also, via the cajo CodebaseServer mechanism, rich internet distributed user interfaces to the service objects can be provided.

The cajo grail framework allows Java Virtual Machines to dynamically distribute their functionality, and user interfaces, across the network transparently. It essentially creates a seamless continuum between cooperating remote Java Virtual Machines, or in other words, a World Wide Virtual Machine. (wwvm) The twelve classes defined in this SDK, along with the included Cajo object, can provide full functional completeness.

A typical cajo server deployment consists minimally of the following seven files:

To view the service client in a full-screen Java Applet, visit the http service, e.g. http://myhost:port/name. (port and name can be omitted if they are 80, and main, respectively, keep the trailing slash though) The application can also be started via WebStart by visiting the server thusly: http://myhost:port/name/! (note the addition of the exclamation mark!) Following the WebStart launch, the system will ask if you wish a shortcut icon placed on the desktop. If yes, clicking on this icon can be used for all subsequent client application launches.

Notes from a network perspective: