Abstract: A system and process for tracking users' usage of content in computer systems. The tracking and accumulation of content usage information allows content providers to understand more about their user base. In a computer system having numerous users, it is advantageous to provide relevant customized content in addition to any specifically requested content. By storing and processing content usage information for users in a computer system, customized content may be provided to a user based on the user's previous usage of similar content. In operation, a computer system hosting various content creates a unique identifier, having data storage space, for a given user of the computer system. When a user sends a request for content to the computer system, a unique identifier is created and/or updated with information relevant to a user's content request. The identifier is passed back to the user with the specifically desired content.

Abstract: Methods for managing the distribution of client bits to client computers are disclosed. The methods of the present invention are particularly suited for use in a network environment in which one or more clients are networked with at least one server via a communications network. The communications network can be a LAN, WAN, intranet, or the Internet. The client version of one or more selected applications software components (the “managed components”) is determined on the client computer. The client queries the server to determine the most current version of each of the managed components. If the client version is not the most current version, or if the client version is missing on the client computer, a determination is made whether to download the most current version onto the client. If the determination is made to install or upgrade one or more managed components, the most current version of each of the selected managed components is downloaded onto the client computer.

Abstract: A service manager for managing services and objects called by browser scripts is employed. The Web browser script is not in direct communication with the service manager; instead, a connector object is mapped by the script into the scripting space. For function calls that the script would previously make to the service or object directly, the script makes a call to a connector object. Depending on the browser brand, the connector object is of a different format e.g., an ActiveX control or a Plug-In. The first time such a connector object is created and mapped into a scripting space, the service manager is initiated and all of the services and objects that are managed by the service manager are loaded. The connector object packages the function call to a service for interpretation by the service manager. A script wrapper is a small object between the scripting space and the connector object, and allows script to be written without regard to different browser brands.