The MMV system combinines typical client-server concepts and components (e.g. server, database, distributable software objects, etc.) with MMV's unique scalable user interface. MMV can be easily understood by examining a typical user session...

A user logs onto the MMV web site using any Internet connected device. MMV validates the user, then determines the capabilities of the user's access device (screen resolution, input method, processing capability, etc.) The appropriate MMV system components are then transferred to the device See Fig. 1.
MMV begins execution on the target device and the MMV desktop appears See Fig 2. As bandwidth permits, MMV begins populating successive hierarchal levels of its desktop interface as background activity.
As a user selects applications, documents, or services in the four main panels, the MMV server transfers code and resource objects as neccessary to support the selected operation. A functioning app, doc, or service is typically provided within a window in the central portion of the desktop See Fig. 3.
As a user opens, views, and manipulates deeper branches of the MMV interface hierarchy, additional structural levels, item information, and icons are supplied by the MMV server See Fig 4.
When a user is finished using the MMV system, her or she simply closes the interface and is logged off automatically.

Throughout an MMV session, the MMV server performs background transfers of low-priority data using spare bandwidth. This data includes communications, such as email and instant messaging, as well as advertising data intended for the Things panel.

Page 1 of 1


(illustrations are currently being updated)