|
Mandala Components Mandala components communicate by exchanging
HTTP-like messages consisting of ASCII headers and optional ASCII
or binary data. Mandala components are shown as white boxes in the
diagram, while standard components that are used without modification
are shown as solid grey shapes. Light grey outlines indicate runtime
constraints. |
||
| Mandala Clients are viewers and editors for groups of web page representations. The clients handle layout, animation, and user interactions, such as direct manipulation of images into groups, creation and editing of imagemaps, and selection of images to access associated information. The clients can run as applications or applets (with reduced functionality). There is a separate client for each Mandala user. Each client needs to make just one socket connection to another process — the Mandala Server. | Mandala clients | 
Mandala client application July 1999 |
| Mandala's proxy server, Mirage, retrieves and caches resources for multiple concurrent clients. Unlike regular proxy servers, Mirage has been extended to monitor requests, helping trusted applications determine which Web pages a user is viewing. Mirage also provides applications with information about the contents of its cache and parses HTML to help applications find web page titles, images, and links. |
proxy server | mirage |
| Mandala's Image Server, Imago, makes thumbnails and imagemaps of Web images. | image server | imago |
| The Mandala Server is the central repository for associations of representations with web pages. It handles the requests from multiple Mandala clients, and stores their associations, group definitions, and imagemaps as HTML files on an associated web server. | Mandala server | |
Mandala | applications | thumbnails | layouts | imagemaps | components | documentation
