US20050021698A1 - Virtual environment manager for network computers - Google Patents
Virtual environment manager for network computers Download PDFInfo
- Publication number
- US20050021698A1 US20050021698A1 US10/877,089 US87708904A US2005021698A1 US 20050021698 A1 US20050021698 A1 US 20050021698A1 US 87708904 A US87708904 A US 87708904A US 2005021698 A1 US2005021698 A1 US 2005021698A1
- Authority
- US
- United States
- Prior art keywords
- services
- service
- vem
- network
- access
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/35—Network arrangements, protocols or services for addressing or naming involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/101—Access control lists [ACL]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Definitions
- This invention relates to network computing. More specifically, this invention relates to methods and means for providing access to network services (for example, system services such as printing and local storage) to applications executing on network connected computers.
- network services for example, system services such as printing and local storage
- Network Computers As the network computing paradigm becomes ubiquitous, simplified inexpensive desktop computers, known as the Network Computers, that have no means of independent existence will become common place. Such devices may run a low function operating system (for simplicity) and rely on servers for basic system services including local storage, printing, and monitoring. While traditional clients, such as PCs, provide their own basic system services they are also likely to seek additional services from the network.
- a downloadable middleware called the Virtual Environment Manager (VEM) is provided.
- VEM allows applications to be developed completely independently of the architecture and environment of a client computer and the servers it connects to.
- client i.e., a network computer
- the VEM queries a Service Directory Table available on one or more connected servers.
- the access to the Service Directory Table returns a handle, which is used to connect to the indicated service provider.
- FIG. 1 depicts a loosely coupled system suitable for use with the present invention
- FIG. 2 show the flow chart for the boot phase of the network computer
- FIG. 3 shows the flow chart for initial steps taken by each service provider
- FIG. 4 shows an instance of the system state with the VEM configured
- FIG. 5 shows the flow control process for an application when it wishes to use a network service
- FIG. 6 shows an example desktop.
- FIG. 1 A loosely coupled system suitable for use with the present invention is illustrated in FIG. 1 .
- the system includes several computers 102 - 106 interconnected by way of a communication network 112 .
- Some of these computers are known as Network Computers 106 ( 1 ), 106 ( 2 ), because they rely on services available via the network to provide many of their basic functions.
- Others are known as service providers 104 ( 1 ), 104 ( 2 ), 104 ( 3 ) because they provide network services, such as basic system services, to the Network Computers.
- Some of the computers are also known as Service Directory Managers (SDMs) 102 , because they maintain a list of services that are provided to network computers by the service providers.
- SDMs Service Directory Managers
- the Network Computers 106 can be embodied, for example, on a JAVA terminal, a personal digital assistant (PDA) or an internet terminal.
- the communication protocol is HTTP and TCP/IP.
- the network 112 can be, for example, a token ring.
- the service systems 102 , 104 ( 1 ), 104 ( 2 ), 104 ( 3 ) can be embodied, for example, on IBM RISC System/6000 machines using AIX 4.2.
- a logical organization can be placed on the physical system desrcibed above.
- This organization can be described by a three tier client/server strategy.
- tier 1 represents the client function
- tier 2 represents the service provider
- tier 3 represents the data object server (i.e., information storage).
- the system described in the present embodiment relates to tiers 1 and 2 and the interface in between.
- the interface in between tiers 2 and 3 is unrestricted, so users can rely on conventional, tried and true data information access systems.
- a service provider can be designed to either reside completely on a tier 2 server or to allocate its function between tiers 1 and 2 by providing a special service stub.
- Each Network Computer includes a Virtual Environment Manager (VEM) 108 ( 1 ), 108 ( 2 ) that is downloaded from a Service Provider by way of the communication network 112 .
- the VEM is embodied as program code instantiated in the random access memory (not shown) of the Network Computer.
- the VEM provides a base class called VEMCLASS (defined in Appendix A) that it relies on for defining a collection of objects (in the sense of “object oriented programming”).
- VEMCLASS defined in Appendix A
- One of the objects included in each VEM is an active entity called the Virtual Environment Superviser (VES) 109 ( 1 ), 109 ( 2 ) that is responsible for maintaining the VEM state.
- VES Virtual Environment Superviser
- the VES is an active JAVA object and is directly instantiated from the VEMCLASS.
- the VEM state includes a table of configured services 110 ( 1 ), 110 ( 2 ) and a table of active applications 112 ( 2 ), 112 ( 2 ). Both the table of configured services and the table of active applications are also instantiated in the random access memory of each Network Computer. Applications inherit from the VEMCLASS in order to interact with the VES. The object class is compiled with the application and bound to the name space of the application.
- a network computer when switched on, it goes through a boot process in which it readies itself for use. At the end of the boot process, the network computer prompts the user for identification.
- the identification process can be, for example, typing in the user name and a password.
- the network computer presents the user with a desktop environment.
- the desktop environment is preferably a JAVA container.
- the JAVA container runs on top of a JAVA virtual machine. Both the container and the JAVA virtual machine are provided by a program such as a Web Browser 114 ( 1 ), 114 ( 2 ) (e.g. Netscape Navigator) which executes on the Network Computer.
- the browser can be downloaded during the Network Computer's boot sequence or provided as an integral part of the Network Computer.
- the browser downloads the VES and a configuration file for the user from a Service Provider.
- the VES uses the configuration file to set up the user's desktop environment (desktop).
- An example desktop (which can be in the form of a home page) is shown in FIG. 6 .
- the configuration file contains a list of system and application services that the user accesses most frequently. These system and application services can be embodied as icons 602 or buttons 604 and/or a textual list 606 displayed on the desktop.
- the system and application services can be accessed as hyperlinks or as direct control buttons where the appropriate JAVA code has been downloaded.
- the remainder of the VEM is downloaded with user applications.
- step 202 the Network Computer is powered on or reset by a user.
- step 204 the Network Computer commences its machine specific, conventional boot sequence. This sequence can be extended to include downloading of the Web browser.
- step 206 the Network Computer prompts the user for a username and password.
- the Network Computer uses conventional methods to determine if the username and password are valid in step 208 . Those of skill in the art will recognize that steps 206 and 208 could alternatively be performed as part of step 204 . If step 208 determines that either the username or password are not valid, the method returns to step 206 . If the username and password are valid, in step 210 the Network Computer downloads the VES and the configuration file.
- the configuration file can be of a conventional flat file format.
- the configuration file can be in the form of a Bookmarks file of the type used by Netscape Navigator 3.0. This configuration is performed by contacting the appropriate service providers and initializing the client's table of services 110 with the server information. Stubs are also downloaded for those services that reside on both tiers 1 and 2 .
- the VES has access to all services available on the network. This enables a user to add any available service to the desktop and as a result to the user's configuration file.
- Service access is provided by a Service Directory Manager (SDM) that maintains a table of services referred to as the Service Directory Table (SDT) 114 (shown in FIG. 1 ).
- SDM Service Directory Manager
- SDT Service Directory Table
- the Service Directory Table contains information about system and application services offered by the Service Providers on the network. It should be understood that there can be a plurality of SDMs on the network, each maintaining a SDT or accessing a single instance of the SDT.
- a Service Provider When a Service Provider is connected to the network, it announces the set of services it offers to the SDM. The steps taken by each Service Provider in announcing the set of services it offers are shown in FIG. 3 .
- the Service Provider In step 302 the Service Provider generates a list of services that it offers.
- the Service Provider identifies the SDM that is responsible for maintaining the list of services in the network.
- the Service Provider scans the list of services and determines the next service to be registered. If there is another service to be registered, in step 308 the Service Provider sends a REGISTER message to the SDM (directory M) and then returns to step 306 . If there are no more services in the list, initialization is completed in step 310 . It should be understood that steps 306 and 308 can be replaced with a single step in which the entire list is read only once and then sent to the appropriate SDM as part of a single message or message sequence.
- FIG. 4 An instance of the system state in which various client stubs are located at the Network Computers is shown in FIG. 4 .
- the Figure shows three Service Providers: a Print Server 402 , a Fax Server 404 and a Mail Server 406 .
- the SDT 408 includes information about the three service providers. In particular, the information describes the type (attribute) of service and the location of the Service Provider which provides the particular service.
- the particular instance of the Network Computer 410 includes various applications 412 (AP 1 -APn), an active VES object 414 which contains a table of configured services and passive stub objects 416 (Print Client Stub, Fax Client Stub, Mail Client Stub) that provide connections to the services.
- the VEM includes the VES, the stubs and the VEMCLASS portion of each application.
- FIG. 5 shows the flow control process for an application when it wishes to use a network service.
- loading the VES into a client is analogous to looking at an HTML page in a browser.
- the VES is downloaded and it's init( ) method is called.
- the init( ) method synchronizes itself to ensure that the class variable VE_supervisor is initialized only once. Any subsequent attempts to start a VES are disabled.
- the class variable, num_AFE is then incremented.
- a registry that contains the Configured Services Table 110 and the Table of Applications 112
- a shared_services table are created.
- a directory services remote object is instantiated, using the DS_server parameters passed in the html file.
- APs can be downloaded.
- APs are assumed to be applets in this discussion.
- the VEM supports applications, though applets are preferred for improved manageability.
- an AP should call the registerAFE( ) method. This call sets the AP's instance variable, VEM_id, to the class variable num_AFE, and increments num_AFE. Since nu_AFE is never decremented, the AP now has a unique id.
- the VES is then called to create an entry for the AP in the registry (the Table of Applications 112 ).
- the entry contains only the applet object reference, id and name, but it can be expanded later as needed.
- the registerAFE( ) method returns a unique key, called a “cookie”, to the AP to ensure that access to the AP information in the registry is controlled.
- the AP is now fully integrated into the VEM environment and is now capable of VEM function.
- the AP When the AP needs a service, it first requests the VEM to register the service using one of the registerService( ) methods. On service registration the VES checks the directory service (the SDM) using the LookupService( ) method to get the handle to the service and to see if the service has a stub. If it does, the stub is downloaded. The VEM then adds a service entry to the registry (the Configured Services Table 112 ) that includes the service's handle and, if appropriate, a reference to the stub. A cookie is passed back to the AP. Once the service is in the registry, both the AP and the VES can access it as needed.
- registerservice( ) method The choice of which registerservice( ) method is called depends on: (1) whether a generic service is needed (i.e. one identifiable with just a name), or whether a more custom service is needed (e.g. one that is identified with a list of attributes as well as a name); and (2) whether the service shared. If the service is not shared, then the AP registering the service is the only one that gets access to the cookie. Otherwise, if the service is present, a cookie is passed back that is the same as those given to other APs for the service. If a shared service is not yet available in the VEM, the shared_service variable is updated to reflect the availability of a new, shared service, and a new cookie is passed back to the AP.
- Access to shared services can be controlled using an access control list.
- shared services can be globally available, i.e. any AP can receive the cookie for the service just by asking for the service.
- Shared services are useful for minimizing the number, of server stubs resident on a client. They can also be useful if service behavior changes caused by one AP are used by another interactively.
- Shared services can be removed from the VEM in various ways.
- a reference count is kept for each service.
- the reference indicates how many APs currently have access to the service. When the reference count reaches zero, the service is removed by the VES. According to an alternative embodiment, only the AP that originally brought in the service is allowed to remove it.
- the AP can get the handle by issuing the getServiceHandle( ) method, or get the stub by using the getServiceInstance( ) method. The AP is then free to make a connection of any sort and use the service.
- the VEM can be embodied to restrict how an AP and service communicate. When the service is no longer needed, the AP calls the RevokeService( ) method that updates the VEM state as follows: if the service is unique to the AP then the service is removed; if the service is a shared service then it is removed in accordance with the rules discussed above.
Abstract
A system and method for a downladable 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 hanlde to the appropriate service to complete the service request.
Description
- a. Field of the Invention
- This invention relates to network computing. More specifically, this invention relates to methods and means for providing access to network services (for example, system services such as printing and local storage) to applications executing on network connected computers.
- b. Related Art
- As the network computing paradigm becomes ubiquitous, simplified inexpensive desktop computers, known as the Network Computers, that have no means of independent existence will become common place. Such devices may run a low function operating system (for simplicity) and rely on servers for basic system services including local storage, printing, and monitoring. While traditional clients, such as PCs, provide their own basic system services they are also likely to seek additional services from the network.
- Existing approaches used to provide these basic system services to applications include the existence of a full-feature operating environment on the Network Computer and/or the requirment that each application provide its own set of needed services. The former approach is not feasible for network clients because these computers are not necessarily equipped with adequate physical resources such as physical memory and attached peripheral devices (e.g., disk drives) to support a full-feature operating environment (e.g., in the case of a Network Computer). The latter approach has the drawback of making each application aware of the platform and environment it can be run under so that it can provide support for necessary basic system services. Further, the former approach adds to the cost of the network clients, while the latter approach adds to the complexity in the design of applications.
- It is an object of the present invention to provide a flexible, powerful, and portable means for enabling network based services for clients.
- In a preferred embodiment, a downloadable middleware called the Virtual Environment Manager (VEM) is provided. The VEM allows applications to be developed completely independently of the architecture and environment of a client computer and the servers it connects to. For a client (i.e., a network computer) to access a service, the VEM queries a Service Directory Table available on one or more connected servers. The access to the Service Directory Table returns a handle, which is used to connect to the indicated service provider.
- The present invention will be understood by reference to the drawing, wherein:
-
FIG. 1 depicts a loosely coupled system suitable for use with the present invention; -
FIG. 2 show the flow chart for the boot phase of the network computer; -
FIG. 3 shows the flow chart for initial steps taken by each service provider; -
FIG. 4 shows an instance of the system state with the VEM configured; -
FIG. 5 shows the flow control process for an application when it wishes to use a network service; and, -
FIG. 6 shows an example desktop. - A loosely coupled system suitable for use with the present invention is illustrated in
FIG. 1 . The system includes several computers 102-106 interconnected by way of acommunication network 112. Of these computers, some are known as Network Computers 106(1), 106(2), because they rely on services available via the network to provide many of their basic functions. Others are known as service providers 104(1), 104(2), 104(3) because they provide network services, such as basic system services, to the Network Computers. Some of the computers are also known as Service Directory Managers (SDMs) 102, because they maintain a list of services that are provided to network computers by the service providers. - The Network Computers 106 can be embodied, for example, on a JAVA terminal, a personal digital assistant (PDA) or an internet terminal. The communication protocol is HTTP and TCP/IP. The
network 112 can be, for example, a token ring. Theservice systems 102, 104(1), 104(2), 104(3) can be embodied, for example, on IBM RISC System/6000 machines using AIX 4.2. - A logical organization can be placed on the physical system desrcibed above. This organization can be described by a three tier client/server strategy. In this strategy,
tier 1 represents the client function,tier 2 represents the service provider andtier 3 represents the data object server (i.e., information storage). The system described in the present embodiment relates totiers tiers tier 2 server or to allocate its function betweentiers - Each Network Computer includes a Virtual Environment Manager (VEM) 108(1), 108(2) that is downloaded from a Service Provider by way of the
communication network 112. The VEM is embodied as program code instantiated in the random access memory (not shown) of the Network Computer. In particular, the VEM provides a base class called VEMCLASS (defined in Appendix A) that it relies on for defining a collection of objects (in the sense of “object oriented programming”). One of the objects included in each VEM is an active entity called the Virtual Environment Superviser (VES) 109(1), 109(2) that is responsible for maintaining the VEM state. In a preferred embodiment, the VES is an active JAVA object and is directly instantiated from the VEMCLASS. The VEM state includes a table of configured services 110(1), 110(2) and a table of active applications 112(2), 112(2). Both the table of configured services and the table of active applications are also instantiated in the random access memory of each Network Computer. Applications inherit from the VEMCLASS in order to interact with the VES. The object class is compiled with the application and bound to the name space of the application. - According to an embodiment of the present invention, when a network computer is switched on, it goes through a boot process in which it readies itself for use. At the end of the boot process, the network computer prompts the user for identification. The identification process can be, for example, typing in the user name and a password. After user identity verification, the network computer presents the user with a desktop environment.
- The desktop environment is preferably a JAVA container. The JAVA container runs on top of a JAVA virtual machine. Both the container and the JAVA virtual machine are provided by a program such as a Web Browser 114(1), 114(2) (e.g. Netscape Navigator) which executes on the Network Computer. The browser can be downloaded during the Network Computer's boot sequence or provided as an integral part of the Network Computer.
- As part of the initialization process, the browser downloads the VES and a configuration file for the user from a Service Provider. The VES uses the configuration file to set up the user's desktop environment (desktop). An example desktop (which can be in the form of a home page) is shown in
FIG. 6 . The configuration file contains a list of system and application services that the user accesses most frequently. These system and application services can be embodied asicons 602 orbuttons 604 and/or atextual list 606 displayed on the desktop. The system and application services can be accessed as hyperlinks or as direct control buttons where the appropriate JAVA code has been downloaded. The remainder of the VEM is downloaded with user applications. - The initial logging and download of the home page is described in
FIG. 2 . Instep 202 the Network Computer is powered on or reset by a user. In response, instep 204 the Network Computer commences its machine specific, conventional boot sequence. This sequence can be extended to include downloading of the Web browser. Instep 206, the Network Computer prompts the user for a username and password. The Network Computer uses conventional methods to determine if the username and password are valid instep 208. Those of skill in the art will recognize thatsteps step 204. Ifstep 208 determines that either the username or password are not valid, the method returns to step 206. If the username and password are valid, instep 210 the Network Computer downloads the VES and the configuration file. - When a VES is downloaded for a user, it initiates configuration of all services that are in the configuration file. The configuration file can be of a conventional flat file format. For example, the configuration file can be in the form of a Bookmarks file of the type used by Netscape Navigator 3.0. This configuration is performed by contacting the appropriate service providers and initializing the client's table of
services 110 with the server information. Stubs are also downloaded for those services that reside on bothtiers - In addition to the currently configured services, the VES has access to all services available on the network. This enables a user to add any available service to the desktop and as a result to the user's configuration file.
- Service access is provided by a Service Directory Manager (SDM) that maintains a table of services referred to as the Service Directory Table (SDT) 114 (shown in
FIG. 1 ). The Service Directory Table contains information about system and application services offered by the Service Providers on the network. It should be understood that there can be a plurality of SDMs on the network, each maintaining a SDT or accessing a single instance of the SDT. - When a Service Provider is connected to the network, it announces the set of services it offers to the SDM. The steps taken by each Service Provider in announcing the set of services it offers are shown in
FIG. 3 . Instep 302 the Service Provider generates a list of services that it offers. Instep 304, the Service Provider identifies the SDM that is responsible for maintaining the list of services in the network. Instep 306 the Service Provider scans the list of services and determines the next service to be registered. If there is another service to be registered, instep 308 the Service Provider sends a REGISTER message to the SDM (directory M) and then returns to step 306. If there are no more services in the list, initialization is completed instep 310. It should be understood thatsteps - An instance of the system state in which various client stubs are located at the Network Computers is shown in
FIG. 4 . The Figure shows three Service Providers: aPrint Server 402, aFax Server 404 and aMail Server 406. TheSDT 408 includes information about the three service providers. In particular, the information describes the type (attribute) of service and the location of the Service Provider which provides the particular service. The particular instance of theNetwork Computer 410 includes various applications 412 (AP1-APn), anactive VES object 414 which contains a table of configured services and passive stub objects 416 (Print Client Stub, Fax Client Stub, Mail Client Stub) that provide connections to the services. The VEM includes the VES, the stubs and the VEMCLASS portion of each application. - The VEM will now be discussed in more detail. For reference, code definitions for the VEM include the VEMCLASS and the client and server interfaces. These are is shown in appendices A and B respectively.
FIG. 5 shows the flow control process for an application when it wishes to use a network service. As previously discussed, loading the VES into a client is analogous to looking at an HTML page in a browser. The VES is downloaded and it's init( ) method is called. The init( ) method synchronizes itself to ensure that the class variable VE_supervisor is initialized only once. Any subsequent attempts to start a VES are disabled. The VES assigns itself id=0 by setting the VEM_id instance variable. The class variable, num_AFE, is then incremented. A registry (that contains the Configured Services Table 110 and the Table of Applications 112) and a shared_services table are created. Finally, a directory services remote object is instantiated, using the DS_server parameters passed in the html file. - Once the VEM has been downloaded and initialized, applications (APs) can be downloaded. (Note that APs are assumed to be applets in this discussion. The VEM supports applications, though applets are preferred for improved manageability.) In it's init( ) method, an AP should call the registerAFE( ) method. This call sets the AP's instance variable, VEM_id, to the class variable num_AFE, and increments num_AFE. Since nu_AFE is never decremented, the AP now has a unique id. The VES is then called to create an entry for the AP in the registry (the Table of Applications 112). At this time, the entry contains only the applet object reference, id and name, but it can be expanded later as needed. The registerAFE( ) method returns a unique key, called a “cookie”, to the AP to ensure that access to the AP information in the registry is controlled. The AP is now fully integrated into the VEM environment and is now capable of VEM function.
- When the AP needs a service, it first requests the VEM to register the service using one of the registerService( ) methods. On service registration the VES checks the directory service (the SDM) using the LookupService( ) method to get the handle to the service and to see if the service has a stub. If it does, the stub is downloaded. The VEM then adds a service entry to the registry (the Configured Services Table 112) that includes the service's handle and, if appropriate, a reference to the stub. A cookie is passed back to the AP. Once the service is in the registry, both the AP and the VES can access it as needed.
- The choice of which registerservice( ) method is called depends on: (1) whether a generic service is needed (i.e. one identifiable with just a name), or whether a more custom service is needed (e.g. one that is identified with a list of attributes as well as a name); and (2) whether the service shared. If the service is not shared, then the AP registering the service is the only one that gets access to the cookie. Otherwise, if the service is present, a cookie is passed back that is the same as those given to other APs for the service. If a shared service is not yet available in the VEM, the shared_service variable is updated to reflect the availability of a new, shared service, and a new cookie is passed back to the AP.
- Access to shared services can be controlled using an access control list. Alternatively, shared services can be globally available, i.e. any AP can receive the cookie for the service just by asking for the service. Shared services are useful for minimizing the number, of server stubs resident on a client. They can also be useful if service behavior changes caused by one AP are used by another interactively.
- Shared services can be removed from the VEM in various ways. According to a first embodiment, a reference count is kept for each service. The reference indicates how many APs currently have access to the service. When the reference count reaches zero, the service is removed by the VES. According to an alternative embodiment, only the AP that originally brought in the service is allowed to remove it.
- Once the VEM state has been updated to include the service, the AP can get the handle by issuing the getServiceHandle( ) method, or get the stub by using the getServiceInstance( ) method. The AP is then free to make a connection of any sort and use the service. The VEM can be embodied to restrict how an AP and service communicate. When the service is no longer needed, the AP calls the RevokeService( ) method that updates the VEM state as follows: if the service is unique to the AP then the service is removed; if the service is a shared service then it is removed in accordance with the rules discussed above.
- Now that the invention has been described by way of the preferred embodiment, various modifications and improvements will occur to those of skill in the art. Thus, it should be understood that the preferred embodiment has been provided as an example and not as a limitation. The scope of the invention is defined by the appended claims.
Claims (3)
1-18. (canceled)
19. A method for providing on-demand access to and interaction with system services to applications executing on a network computer, comprising the steps of:
a) in response to a demand from a user, downloading executable code comprising a virtual environment manager for providing access to remote network system and application services;
b) identifying a set of system and application services;
c) configuring the set of system and application services by contacting a plurality of appropriate remote service providers for each particular one of the system and application services and downloading one of client stubs and a handle for each one of the service providers;
d) maintaining a list of configured services; and
e) providing access to the configured services.
20. The method of claim 19 comprising the further step of sharing access to the system services by a plurality of the applications.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/877,089 US20050021698A1 (en) | 1996-10-07 | 2004-06-25 | Virtual environment manager for network computers |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/722,434 US6757729B1 (en) | 1996-10-07 | 1996-10-07 | Virtual environment manager for network computers |
US10/877,089 US20050021698A1 (en) | 1996-10-07 | 2004-06-25 | Virtual environment manager for network computers |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/722,434 Division US6757729B1 (en) | 1996-10-07 | 1996-10-07 | Virtual environment manager for network computers |
Publications (1)
Publication Number | Publication Date |
---|---|
US20050021698A1 true US20050021698A1 (en) | 2005-01-27 |
Family
ID=24901817
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/722,434 Expired - Lifetime US6757729B1 (en) | 1996-10-07 | 1996-10-07 | Virtual environment manager for network computers |
US10/877,089 Abandoned US20050021698A1 (en) | 1996-10-07 | 2004-06-25 | Virtual environment manager for network computers |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/722,434 Expired - Lifetime US6757729B1 (en) | 1996-10-07 | 1996-10-07 | Virtual environment manager for network computers |
Country Status (5)
Country | Link |
---|---|
US (2) | US6757729B1 (en) |
JP (1) | JPH10154078A (en) |
KR (1) | KR100287275B1 (en) |
CN (1) | CN1085917C (en) |
GB (1) | GB2320344B (en) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080244575A1 (en) * | 2007-03-30 | 2008-10-02 | Novell, Inc. | Tessellated virtual machines conditionally linked for common computing goals |
US20080256538A1 (en) * | 2007-04-10 | 2008-10-16 | Novell, Inc. | Storage configurations for tessellated virtual machines |
US20080307415A1 (en) * | 2007-06-11 | 2008-12-11 | Novell, Inc. | Tessellated applications for user computing environments |
US20090133017A1 (en) * | 2007-11-15 | 2009-05-21 | Boogert Kevin M | Environment managers via virtual machines |
US20090201830A1 (en) * | 2006-10-31 | 2009-08-13 | Stephane Angelot | Method & system for network entity configuration |
US20100281528A1 (en) * | 2009-05-02 | 2010-11-04 | Richard Hayton | Methods and systems for generating and delivering an interactive application delivery store |
US8762525B2 (en) * | 2012-03-08 | 2014-06-24 | International Business Machines Corporation | Managing risk in resource over-committed systems |
US11456071B2 (en) | 2010-04-08 | 2022-09-27 | Hemosonics Llc | Hemostatic parameter display |
Families Citing this family (66)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6272559B1 (en) * | 1997-10-15 | 2001-08-07 | Sun Microsystems, Inc. | Deferred reconstruction of objects and remote loading for event notification in a distributed system |
US6185611B1 (en) | 1998-03-20 | 2001-02-06 | Sun Microsystem, Inc. | Dynamic lookup service in a distributed system |
US6466947B2 (en) * | 1998-03-20 | 2002-10-15 | Sun Microsystems, Inc. | Apparatus and method for dynamically verifying information in a distributed system |
US6393497B1 (en) | 1998-03-20 | 2002-05-21 | Sun Microsystems, Inc. | Downloadable smart proxies for performing processing associated with a remote procedure call in a distributed system |
JP3758193B2 (en) * | 1996-08-02 | 2006-03-22 | セイコーエプソン株式会社 | Network system |
US6757729B1 (en) * | 1996-10-07 | 2004-06-29 | International Business Machines Corporation | Virtual environment manager for network computers |
JP2002505467A (en) * | 1998-02-26 | 2002-02-19 | サン・マイクロシステムズ・インコーポレーテッド | Dynamic reference service in distributed systems |
WO1999044296A2 (en) * | 1998-02-26 | 1999-09-02 | Sun Microsystems, Inc. | Apparatus and method for dynamically verifying information in a distributed system |
US20020046228A1 (en) * | 1998-03-20 | 2002-04-18 | Sun Microsystems, Inc. | Method and system for facilitating access to a lookup service |
US6125391A (en) * | 1998-10-16 | 2000-09-26 | Commerce One, Inc. | Market makers using documents for commerce in trading partner networks |
US6581088B1 (en) | 1998-11-05 | 2003-06-17 | Beas Systems, Inc. | Smart stub or enterprise javaTM bean in a distributed processing system |
US8165155B2 (en) | 2004-07-01 | 2012-04-24 | Broadcom Corporation | Method and system for a thin client and blade architecture |
WO2000036803A1 (en) * | 1998-12-16 | 2000-06-22 | Siemens Aktiengesellschaft | Service system in a network |
JP2000339246A (en) * | 1999-05-26 | 2000-12-08 | Takaoka Electric Mfg Co Ltd | Network device |
GB9915301D0 (en) | 1999-06-30 | 1999-09-01 | Nokia Telecommunications Oy | Service management |
US6711157B1 (en) * | 1999-08-24 | 2004-03-23 | Telefonaktiebolaget L M Ericsson (Publ) | System and method of creating subscriber services in an IP-based telecommunications network |
JP4383625B2 (en) | 2000-03-16 | 2009-12-16 | キヤノン株式会社 | Distributed processing system and control method thereof |
US7127526B1 (en) * | 2000-03-20 | 2006-10-24 | Nortel Networks Limited | Method and apparatus for dynamically loading and managing software services on a network device |
US6981041B2 (en) * | 2000-04-13 | 2005-12-27 | Aep Networks, Inc. | Apparatus and accompanying methods for providing, through a centralized server site, an integrated virtual office environment, remotely accessible via a network-connected web browser, with remote network monitoring and management capabilities |
US7165113B2 (en) * | 2000-11-28 | 2007-01-16 | Hewlett-Packard Development Company, L.P. | Computer language for defining business conversations |
US6993506B2 (en) | 2000-12-05 | 2006-01-31 | Jgr Acquisition, Inc. | Method and device utilizing polymorphic data in e-commerce |
US7636757B2 (en) * | 2000-12-15 | 2009-12-22 | Canon Kabushiki Kaisha | Printing over the internet |
JP2002196990A (en) * | 2000-12-27 | 2002-07-12 | Kddi Corp | Service discovery protocol conversion gateway |
US7296275B2 (en) * | 2001-01-04 | 2007-11-13 | Sun Microsystems, Inc. | Method and system for passing objects in a distributed system using serialization contexts |
US7136908B2 (en) * | 2001-01-29 | 2006-11-14 | Intel Corporation | Extensible network services system |
US7249195B2 (en) * | 2001-03-30 | 2007-07-24 | Minor Ventures, Llc | Apparatus and methods for correlating messages sent between services |
US7434234B2 (en) * | 2001-05-04 | 2008-10-07 | Outlooksoft Corporation | Method and system for facilitating communications in a network using on demand distribution |
US6970902B1 (en) * | 2001-05-24 | 2005-11-29 | Cisco Technology, Inc. | Method and apparatus for providing a distributed service in a network |
US7415512B1 (en) * | 2001-05-24 | 2008-08-19 | Cisco Technology, Inc. | Method and apparatus for providing a general purpose computing platform at a router on a network |
US8131870B1 (en) | 2001-05-24 | 2012-03-06 | Cisco Technology, Inc. | Method and apparatus for registering a mobile object on a foreign network |
US7660887B2 (en) | 2001-09-07 | 2010-02-09 | Sun Microsystems, Inc. | Systems and methods for providing dynamic quality of service for a distributed system |
US7756969B1 (en) | 2001-09-07 | 2010-07-13 | Oracle America, Inc. | Dynamic provisioning of identification services in a distributed system |
US20030051029A1 (en) * | 2001-09-07 | 2003-03-13 | Reedy Dennis G. | Dynamic provisioning of sevice components in a distributed system |
US20030051030A1 (en) * | 2001-09-07 | 2003-03-13 | Clarke James B. | Distributed metric discovery and collection in a distributed system |
US8219608B2 (en) * | 2002-06-20 | 2012-07-10 | Koninklijke Philips Electronics N.V. | Scalable architecture for web services |
US20040002883A1 (en) * | 2002-06-27 | 2004-01-01 | Andrews Keith H. | Method for linking solution-specific method and process deliverables to business-based delivery framework |
US20040138961A1 (en) * | 2002-11-08 | 2004-07-15 | Matt Clark | Sevice-vendor request processing for data service processing |
US20060168285A1 (en) * | 2003-04-17 | 2006-07-27 | Nielsen Peter D | File upload using a browser |
EP1505796A1 (en) | 2003-08-06 | 2005-02-09 | STMicroelectronics Limited | Method for controlling services |
EP1709530A2 (en) * | 2004-01-20 | 2006-10-11 | Broadcom Corporation | System and method for supporting multiple users |
US7792874B1 (en) | 2004-01-30 | 2010-09-07 | Oracle America, Inc. | Dynamic provisioning for filtering and consolidating events |
US7802007B2 (en) | 2004-05-19 | 2010-09-21 | Salesforce.Com, Inc. | Techniques for providing connections to services in a network environment |
US7908339B2 (en) * | 2004-06-03 | 2011-03-15 | Maxsp Corporation | Transaction based virtual file system optimized for high-latency network connections |
US9357031B2 (en) * | 2004-06-03 | 2016-05-31 | Microsoft Technology Licensing, Llc | Applications as a service |
US8812613B2 (en) * | 2004-06-03 | 2014-08-19 | Maxsp Corporation | Virtual application manager |
US7664834B2 (en) | 2004-07-09 | 2010-02-16 | Maxsp Corporation | Distributed operating system management |
CN100389564C (en) * | 2005-01-07 | 2008-05-21 | 腾讯科技(深圳)有限公司 | Network service information processing system and method |
JP2006260529A (en) * | 2005-02-16 | 2006-09-28 | Denso Wave Inc | Program-providing system |
US8234238B2 (en) | 2005-03-04 | 2012-07-31 | Maxsp Corporation | Computer hardware and software diagnostic and report system |
US8589323B2 (en) | 2005-03-04 | 2013-11-19 | Maxsp Corporation | Computer hardware and software diagnostic and report system incorporating an expert system and agents |
KR100777426B1 (en) * | 2006-03-29 | 2007-11-22 | (주)닥터소프트 | Application joint service system, Client process module for application joint service providers, and Client process module for application joint service users |
JP2009537892A (en) * | 2006-05-18 | 2009-10-29 | サンギュ イ | How to protect clients and servers |
US8811396B2 (en) | 2006-05-24 | 2014-08-19 | Maxsp Corporation | System for and method of securing a network utilizing credentials |
US8898319B2 (en) | 2006-05-24 | 2014-11-25 | Maxsp Corporation | Applications and services as a bundle |
EP2047380A4 (en) * | 2006-08-01 | 2011-11-09 | Samsung Electronics Co Ltd | System and method for managing user preference profile |
US7840514B2 (en) * | 2006-09-22 | 2010-11-23 | Maxsp Corporation | Secure virtual private network utilizing a diagnostics policy and diagnostics engine to establish a secure network connection |
US9317506B2 (en) | 2006-09-22 | 2016-04-19 | Microsoft Technology Licensing, Llc | Accelerated data transfer using common prior data segments |
US8423821B1 (en) | 2006-12-21 | 2013-04-16 | Maxsp Corporation | Virtual recovery server |
US7844686B1 (en) | 2006-12-21 | 2010-11-30 | Maxsp Corporation | Warm standby appliance |
US20080270641A1 (en) * | 2007-04-30 | 2008-10-30 | Rothwell Rick R | Digital sending device preconfigured to use vendor-provided computer network resources to deliver electronic content |
US8307239B1 (en) | 2007-10-26 | 2012-11-06 | Maxsp Corporation | Disaster recovery appliance |
US8645515B2 (en) | 2007-10-26 | 2014-02-04 | Maxsp Corporation | Environment manager |
US8175418B1 (en) | 2007-10-26 | 2012-05-08 | Maxsp Corporation | Method of and system for enhanced data storage |
TWI351849B (en) * | 2007-12-31 | 2011-11-01 | Ind Tech Res Inst | Apparatus and method for transmitting streaming se |
WO2015013936A1 (en) * | 2013-07-31 | 2015-02-05 | 华为技术有限公司 | Associated plugin management method, device and system |
US9420035B2 (en) * | 2014-02-20 | 2016-08-16 | International Business Machines Corporation | Transaction isolation during multi-tenant transaction requests |
Citations (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4724521A (en) * | 1986-01-14 | 1988-02-09 | Veri-Fone, Inc. | Method for operating a local terminal to execute a downloaded application program |
US5371532A (en) * | 1992-05-15 | 1994-12-06 | Bell Communications Research, Inc. | Communications architecture and method for distributing information services |
US5442771A (en) * | 1988-07-15 | 1995-08-15 | Prodigy Services Company | Method for storing data in an interactive computer network |
US5457797A (en) * | 1993-08-03 | 1995-10-10 | Forte Software, Inc. | Flexible multi-platform partitioning for computer applications |
US5491820A (en) * | 1994-11-10 | 1996-02-13 | At&T Corporation | Distributed, intermittently connected, object-oriented database and management system |
US5517645A (en) * | 1993-11-05 | 1996-05-14 | Microsoft Corporation | Method and system for interfacing components via aggregate components formed by aggregating the components each with an instance of a component manager |
US5526409A (en) * | 1993-10-26 | 1996-06-11 | Visa International Service Association | Adaptive communication system within a transaction card network |
US5550957A (en) * | 1994-12-07 | 1996-08-27 | Lexmark International, Inc. | Multiple virtual printer network interface |
US5557541A (en) * | 1994-07-21 | 1996-09-17 | Information Highway Media Corporation | Apparatus for distributing subscription and on-demand audio programming |
US5790173A (en) * | 1995-07-20 | 1998-08-04 | Bell Atlantic Network Services, Inc. | Advanced intelligent network having digital entertainment terminal or the like interacting with integrated service control point |
US5797010A (en) * | 1995-12-22 | 1998-08-18 | Time Warner Cable | Multiple run-time execution environment support in a set-top processor |
US5956489A (en) * | 1995-06-07 | 1999-09-21 | Microsoft Corporation | Transaction replication system and method for supporting replicated transaction-based services |
US20020029268A1 (en) * | 2000-07-17 | 2002-03-07 | Baca C. Daniel | Intelligent network providing network access services (INP-NAS) |
US20020032765A1 (en) * | 2000-07-17 | 2002-03-14 | David Pezzutti | Intelligent network providing network accss services (INP-NAS) |
US20020166117A1 (en) * | 2000-09-12 | 2002-11-07 | Abrams Peter C. | Method system and apparatus for providing pay-per-use distributed computing resources |
US6496858B1 (en) * | 1997-07-14 | 2002-12-17 | Tut Systems, Inc. | Remote reconfiguration of a secure network interface |
US6560656B1 (en) * | 1998-02-26 | 2003-05-06 | Sun Microsystems, Inc. | Apparatus and method for providing downloadable code for use in communicating with a device in a distributed system |
US6591290B1 (en) * | 1999-08-24 | 2003-07-08 | Lucent Technologies Inc. | Distributed network application management system |
US6604127B2 (en) * | 1998-03-20 | 2003-08-05 | Brian T. Murphy | Dynamic lookup service in distributed system |
US6757729B1 (en) * | 1996-10-07 | 2004-06-29 | International Business Machines Corporation | Virtual environment manager for network computers |
Family Cites Families (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5426421A (en) * | 1986-04-21 | 1995-06-20 | Gray; William F. | Method of automatically managing a network or remote function-excecuting apparatus from a programable network control center |
WO1989002631A1 (en) * | 1987-09-08 | 1989-03-23 | Digital Equipment Corporation | Naming service for networked digital data processing system |
US5341477A (en) * | 1989-02-24 | 1994-08-23 | Digital Equipment Corporation | Broker for computer network server selection |
US5187787B1 (en) * | 1989-07-27 | 1996-05-07 | Teknekron Software Systems Inc | Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processes |
US5261044A (en) * | 1990-09-17 | 1993-11-09 | Cabletron Systems, Inc. | Network management system using multifunction icons for information display |
CA2048306A1 (en) * | 1990-10-02 | 1992-04-03 | Steven P. Miller | Distributed configuration profile for computing system |
US5287507A (en) * | 1992-03-27 | 1994-02-15 | Sun Microsystems, Inc. | Method and apparatus for portable object handles that use local caches |
WO1993020511A1 (en) * | 1992-03-31 | 1993-10-14 | Aggregate Computing, Inc. | An integrated remote execution system for a heterogenous computer network environment |
DE69432199T2 (en) * | 1993-05-24 | 2004-01-08 | Sun Microsystems, Inc., Mountain View | Graphical user interface with methods for interfacing with remote control devices |
AU6702594A (en) * | 1993-12-17 | 1995-07-03 | Taligent, Inc. | Object-oriented distributed communications directory service |
US5483652A (en) | 1994-01-24 | 1996-01-09 | Digital Equipment Corporation | Mechanism for locating without search discrete application resources known by common name only in a distributed network computing environment |
US5838906A (en) * | 1994-10-17 | 1998-11-17 | The Regents Of The University Of California | Distributed hypermedia method for automatically invoking external application providing interaction and display of embedded objects within a hypermedia document |
US5734828A (en) * | 1995-08-30 | 1998-03-31 | Intel Corporation | System for accessing/delivering on-line/information services via individualized environments using streamlined application sharing host and client services |
US6009464A (en) * | 1995-09-20 | 1999-12-28 | Sun Microsystems, Inc. | Method and apparatus for enabling application programs to communicate with network clients and servers |
JP3751664B2 (en) * | 1995-10-05 | 2006-03-01 | 富士通株式会社 | Software registration system and method |
US5778384A (en) | 1995-12-22 | 1998-07-07 | Sun Microsystems, Inc. | System and method for automounting and accessing remote file systems in Microsoft Windows in a networking environment |
US5748896A (en) * | 1995-12-27 | 1998-05-05 | Apple Computer, Inc. | Remote network administration methods and apparatus |
US5826000A (en) * | 1996-02-29 | 1998-10-20 | Sun Microsystems, Inc. | System and method for automatic configuration of home network computers |
US6708171B1 (en) * | 1996-04-23 | 2004-03-16 | Sun Microsystems, Inc. | Network proxy |
US6185611B1 (en) * | 1998-03-20 | 2001-02-06 | Sun Microsystem, Inc. | Dynamic lookup service in a distributed system |
US5802530A (en) * | 1996-07-01 | 1998-09-01 | Sun Microsystems, Inc. | Web document based graphical user interface |
US6131116A (en) * | 1996-12-13 | 2000-10-10 | Visto Corporation | System and method for globally accessing computer services |
US6012100A (en) * | 1997-07-14 | 2000-01-04 | Freegate Corporation | System and method of configuring a remotely managed secure network interface |
US5870544A (en) * | 1997-10-20 | 1999-02-09 | International Business Machines Corporation | Method and apparatus for creating a secure connection between a java applet and a web server |
JP2002505467A (en) * | 1998-02-26 | 2002-02-19 | サン・マイクロシステムズ・インコーポレーテッド | Dynamic reference service in distributed systems |
EP1058884A1 (en) * | 1998-02-26 | 2000-12-13 | Sun Microsystems, Inc. | Method and system for facilitating access to a lookup service |
US6449642B2 (en) * | 1998-09-15 | 2002-09-10 | Microsoft Corporation | Method and system for integrating a client computer into a computer network |
US6266774B1 (en) * | 1998-12-08 | 2001-07-24 | Mcafee.Com Corporation | Method and system for securing, managing or optimizing a personal computer |
AU2001294590A1 (en) * | 2000-09-15 | 2002-03-26 | Motorola, Inc., A Corporation Of The State Of Delaware | Service framework with just-in-time lookup |
-
1996
- 1996-10-07 US US08/722,434 patent/US6757729B1/en not_active Expired - Lifetime
-
1997
- 1997-06-11 KR KR1019970024192A patent/KR100287275B1/en not_active IP Right Cessation
- 1997-09-05 CN CN97118402A patent/CN1085917C/en not_active Expired - Lifetime
- 1997-09-26 GB GB9720400A patent/GB2320344B/en not_active Expired - Lifetime
- 1997-09-30 JP JP9265696A patent/JPH10154078A/en active Pending
-
2004
- 2004-06-25 US US10/877,089 patent/US20050021698A1/en not_active Abandoned
Patent Citations (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4724521A (en) * | 1986-01-14 | 1988-02-09 | Veri-Fone, Inc. | Method for operating a local terminal to execute a downloaded application program |
US5442771A (en) * | 1988-07-15 | 1995-08-15 | Prodigy Services Company | Method for storing data in an interactive computer network |
US5371532A (en) * | 1992-05-15 | 1994-12-06 | Bell Communications Research, Inc. | Communications architecture and method for distributing information services |
US5457797A (en) * | 1993-08-03 | 1995-10-10 | Forte Software, Inc. | Flexible multi-platform partitioning for computer applications |
US5526409A (en) * | 1993-10-26 | 1996-06-11 | Visa International Service Association | Adaptive communication system within a transaction card network |
US5517645A (en) * | 1993-11-05 | 1996-05-14 | Microsoft Corporation | Method and system for interfacing components via aggregate components formed by aggregating the components each with an instance of a component manager |
US5557541A (en) * | 1994-07-21 | 1996-09-17 | Information Highway Media Corporation | Apparatus for distributing subscription and on-demand audio programming |
US5491820A (en) * | 1994-11-10 | 1996-02-13 | At&T Corporation | Distributed, intermittently connected, object-oriented database and management system |
US5550957A (en) * | 1994-12-07 | 1996-08-27 | Lexmark International, Inc. | Multiple virtual printer network interface |
US5956489A (en) * | 1995-06-07 | 1999-09-21 | Microsoft Corporation | Transaction replication system and method for supporting replicated transaction-based services |
US5790173A (en) * | 1995-07-20 | 1998-08-04 | Bell Atlantic Network Services, Inc. | Advanced intelligent network having digital entertainment terminal or the like interacting with integrated service control point |
US5797010A (en) * | 1995-12-22 | 1998-08-18 | Time Warner Cable | Multiple run-time execution environment support in a set-top processor |
US6757729B1 (en) * | 1996-10-07 | 2004-06-29 | International Business Machines Corporation | Virtual environment manager for network computers |
US6496858B1 (en) * | 1997-07-14 | 2002-12-17 | Tut Systems, Inc. | Remote reconfiguration of a secure network interface |
US6560656B1 (en) * | 1998-02-26 | 2003-05-06 | Sun Microsystems, Inc. | Apparatus and method for providing downloadable code for use in communicating with a device in a distributed system |
US6604127B2 (en) * | 1998-03-20 | 2003-08-05 | Brian T. Murphy | Dynamic lookup service in distributed system |
US6591290B1 (en) * | 1999-08-24 | 2003-07-08 | Lucent Technologies Inc. | Distributed network application management system |
US20020029268A1 (en) * | 2000-07-17 | 2002-03-07 | Baca C. Daniel | Intelligent network providing network access services (INP-NAS) |
US20020032765A1 (en) * | 2000-07-17 | 2002-03-14 | David Pezzutti | Intelligent network providing network accss services (INP-NAS) |
US20020166117A1 (en) * | 2000-09-12 | 2002-11-07 | Abrams Peter C. | Method system and apparatus for providing pay-per-use distributed computing resources |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090201830A1 (en) * | 2006-10-31 | 2009-08-13 | Stephane Angelot | Method & system for network entity configuration |
US8089953B2 (en) * | 2006-10-31 | 2012-01-03 | Aastra Technologies Limited | Method and system for network entity configuration |
US20080244575A1 (en) * | 2007-03-30 | 2008-10-02 | Novell, Inc. | Tessellated virtual machines conditionally linked for common computing goals |
US8146080B2 (en) | 2007-03-30 | 2012-03-27 | Novell, Inc. | Tessellated virtual machines conditionally linked for common computing goals |
US20080256538A1 (en) * | 2007-04-10 | 2008-10-16 | Novell, Inc. | Storage configurations for tessellated virtual machines |
US20080307415A1 (en) * | 2007-06-11 | 2008-12-11 | Novell, Inc. | Tessellated applications for user computing environments |
US20090133017A1 (en) * | 2007-11-15 | 2009-05-21 | Boogert Kevin M | Environment managers via virtual machines |
US8930945B2 (en) | 2007-11-15 | 2015-01-06 | Novell, Inc. | Environment managers via virtual machines |
US20100281528A1 (en) * | 2009-05-02 | 2010-11-04 | Richard Hayton | Methods and systems for generating and delivering an interactive application delivery store |
US9152401B2 (en) * | 2009-05-02 | 2015-10-06 | Citrix Systems, Inc. | Methods and systems for generating and delivering an interactive application delivery store |
US11456071B2 (en) | 2010-04-08 | 2022-09-27 | Hemosonics Llc | Hemostatic parameter display |
US8762525B2 (en) * | 2012-03-08 | 2014-06-24 | International Business Machines Corporation | Managing risk in resource over-committed systems |
Also Published As
Publication number | Publication date |
---|---|
GB9720400D0 (en) | 1997-11-26 |
KR19980032159A (en) | 1998-07-25 |
KR100287275B1 (en) | 2001-04-16 |
US6757729B1 (en) | 2004-06-29 |
CN1180968A (en) | 1998-05-06 |
JPH10154078A (en) | 1998-06-09 |
GB2320344A (en) | 1998-06-17 |
GB2320344B (en) | 2001-05-30 |
CN1085917C (en) | 2002-05-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6757729B1 (en) | Virtual environment manager for network computers | |
US6295556B1 (en) | Method and system for configuring computers to connect to networks using network connection objects | |
US6105066A (en) | Client-server system with central application management and using fully qualified class names of object-oriented applications for determining permanent server storage locations for application configuration information | |
US6496511B1 (en) | Method for preserving preassigned IP addresses in a remote access server | |
US6108712A (en) | Client-server system with central application management and providing export agent capability for retrofitting existing hardware and applications into the system | |
KR100421302B1 (en) | System and method for automatic configuration of home network computers | |
US6205476B1 (en) | Client—server system with central application management allowing an administrator to configure end user applications by executing them in the context of users and groups | |
JP3518958B2 (en) | Distributed file system translator with extended attribute support | |
US6237092B1 (en) | Client-server system with central application management allowing an administrator to configure user and group contexts during application configuration without relaunching the application | |
US6871346B1 (en) | Back-end decoupled management model and management system utilizing same | |
US6871286B1 (en) | Method and apparatus for resetting passwords in a computer system | |
US20010011341A1 (en) | Client-server system for maintaining a user desktop consistent with server application user access permissions | |
CN1685323B (en) | Communication system, relay device, and communication control method | |
US20080263543A1 (en) | On-Demand active role-based software provisioning | |
US20030009519A1 (en) | Apparatus and method for processing servlets | |
EP1076973A1 (en) | Client-server system for maintaining application preferences in a hierarchical data structure | |
JP2003288280A (en) | System and method for providing context information | |
EP1449105A1 (en) | Localized read-only storage device for distrubuting files over a network | |
WO2007047639A2 (en) | Discovering network services | |
US6862614B2 (en) | Adaptation of service applications to heterogeneous execution context by means of smart cards | |
Cisco | Provisioning Devices | |
Fernández | Towards interoperability amongst European public administrations | |
Hauck et al. | A middleware architecture for scalable, QoS-aware, and self-organizing global services | |
JP2002244945A (en) | Method and system for supporting connection setting of internet | |
JP2000155726A (en) | Network computer and its log-in method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |