Abstract: A system and method for a downloadable just-in-time middleware called VEM that provides access to network services, including system services such as printing and local storage, to applications that run on Network Computers. The VEM configures the default client services and stores information about these services. When an application executing on the Network Computer wishes to use one of the services, it communicates with its local VEM. The VEM returns a handle to the appropriate service to complete the service request.

Abstract: A system and method of implicitly localizing agent access to a network component located on a remote host includes the steps of determining a host location of the network component; automatically relocating an agent to the remote host; and incorporating the agent into an address space shared by the network component. The agent is preferably a script.

Abstract: An improved method and apparatus for dynamic execution of mobile agents. For example, a symbolic name for a component to be executed can be dynamically resolved using a component directory to determine an appropriate network host that the agent needs to visit. Preferably, the component directory can be queried by client or host machines, and updated by component hosts. Changes in a component's location and/or availability can also be captured at runtime and the agents dynamically routed to alternate component hosts. Still other features enable agents to flexibly accommodate the dynamics of the system. For example, if the attributes of a component are modified, or a component host becomes heavily loaded, agents can adapt to such changes by looking up an alternate host for the same component. Yet other features provide improved system manageability. For example, component hosts can freely update a component's location and/or attributes at any time.

Abstract: A method and apparatus for providing a network computer with secure remote swapping to avoid transmitting active memory resident entities (such as data structures, pages, and segments) containing sensitive data in the clear. When a memory resident entity is created, it is entered in a Table of Secure Entities (TSE) if it requires security. The memory manager of the network computer checks the TSE for an entity before swapping it out to a network server. If the entity is in the TSE, the memory manager encrypts the contents of the entity using the public key from the network computer's SmartCard device. When reloading the entity, the memory manager uses the private key from the SmartCard to decrypt the contents of the entity.