Traditional mainframe computer configurations provided for user interface to the computer through computer terminals which were directly connected by wires to ports of the mainframe computer. As computing technology has evolved, processing power has typically evolved from a central processing center with a number of relatively low-processing power terminals to a distributed environment of networked processors. Examples of this shift in processing include local or wide area computer networks which interconnect individual work stations where each workstation has substantial independent processing capabilities. This shift may be further seen in the popularity of the Internet which interconnects many processors and networks of processors through devices such as, for example, routers. This type of network environment is often referred to as a client-server environment with client stations coupled to and supported by a server station.
In the modern distributed processing computer environment, control over software, such as application programs, is more difficult than where a mainframe operated by an administrator is used, particularly for large organizations with numerous client stations and servers distributed widely geographically and utilized by a large number of users. Furthermore, individual users may move from location to location and need to access the network from different client stations at different times. The networked environment increases the challenges for a network administrator in maintaining proper licenses for existing software and deploying new or updated application programs across the network.
A further complication in network systems is that, typically, these systems include combinations of network applications and native applications as well as combinations of different connection types and hardware devices. As used herein “native applications” refers to applications which are installed locally on a workstation such that characteristics associated with the native application are stored on the workstation. The combinations of network connections, differing hardware, native applications and network applications makes portability of preferences or operating environment characteristics which provide consistency from workstation to workstation difficult. Furthermore, differences in hardware or connections may create inefficiencies as users move from workstation to workstation. For example, a user may, in a first session, access the network utilizing a high speed connection and a workstation with a high resolution color monitor to execute an application and then, in a later session, access the network to execute the same application from a mobile computer with a monochrome display and a low speed modem connection to the network. Thus, session content, such as color display data or preferences associated with the application, which may have been appropriate for the first session may be inappropriate or inefficient in a later session.
Efforts to address mobility of uses in a network have included efforts to provide preference mobility such as, for example, Novell's Z.E.N.works™, Microsoft's “Zero Administration” initiative for Windows® and International Business Machines Corporation's (IBM's) Workspace On Demand™. However, these solutions each typically require pre-installation of software at the workstation to support their services. For example, Novell's Z.E.N. and IBM's Workspace On Demand utilize a vendor-supplied support layer in the operating system to enable their services. In addition to modifying the workstations operating system at startup to setup tasks to customize the user's environment, the Microsoft Zero Administration solution may be limited to a homogeneous environment where the workstation and the server are utilizing the same operating system.
Each of these “mobility” systems typically do not address the full range of complications which may arise in a heterogeneous network utilizing differing devices and connections. Users would typically have to manually define session characteristics at each differing workstation they used in the network or maintain local characteristic definitions which may be inappropriate for particular applications a user is executing and may substantially reduce the administrative convenience of a centrally controlled network. Thus, these various approaches fail to provide a seamless integration of session characteristics across heterogeneous network devices. Such solutions may reduce network administration only after initial installation on each workstation. Furthermore, content is typically not addressed such that inefficiencies in use of the network may result.