Mechanism for enabling customized session managers to interact with a network server

• US 20040064564A1
• Filed: 09/18/2003
• Published: 04/01/2004
• Est. Priority Date: 09/24/1999
• Status: Active Grant

• Current Assignee: Ruslan Belkin
• Original Assignee: Ruslan Belkin
• Inventors: Belkin, Ruslan
• Granted Patent: US 6,944,666 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: G06F 2209/5016 Session
• CPC Class Codes: G06F 2209/5018 Thread allocation
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine
• CPC Class Codes: H04L 67/01 Protocols

Abstract

A mechanism for enabling customized session managers to interact with a network server is disclosed. A programming interface enables customized session managers to “plug in” to and to interact with the server, making it possible to change session management functionality without having to make any changes to the core server. It also makes it possible to incorporate multiple session managers into the server. These aspects of the programming interface significantly increase the flexibility and scalability of the web server. The mechanism further includes a service engine for coordinating the interaction with the session managers. For each client request, the service engine determines which application needs to be invoked. Then, based upon that application, the service engine determines which, if any, associated session manager needs to be invoked to manage session (i.e. state) information for that application. The service engine invokes the session manager via the programming interface.

Claims

1. A computer implemented method for servicing client requests, comprising:

receiving multiple associated client requests;

in response to each of said associated client requests;

invoking an application;

determining, based upon said application, a session manager to associate with said application; and

invoking said session manager to manage state information for said application across said multiple associated client requests.

2. The method of claim 1, wherein said session manager is invoked via a programming interface.

3. The method of claim 2, wherein said programming interface comprises a definition of an abstract class, and wherein said session manager is a subclass of said abstract class.

4. The method of claim 3, wherein said session manager comprises an implementation for each method defined for said abstract class, and wherein said session manager is invoked by invoking a particular method implementation provided by said session manager.

5. The method of claim 1, wherein said associated client requests are associated with each other by way of a session ID.

6. The method of claim 1, wherein determining a session manager to associate with said application comprises:

accessing a set of configuration information which specifies which session manager to associate with said application.

7. An apparatus for servicing client requests, comprising:

a mechanism for receiving multiple associated client requests; and

a mechanism for responding to each of said associated client requests by;

invoking an application;

determining, based upon said application, a session manager to associate with said application; and

invoking said session manager to manage state information for said application across said multiple associated client requests.

8. The apparatus of claim 7, wherein said apparatus further comprises a programming interface, and wherein said session manager is invoked via said programming interface.

9. The apparatus of claim 8, wherein said programming interface comprises a definition of an abstract class, and wherein said session manager is a subclass of said abstract class.

10. The apparatus of claim 9, wherein said session manager comprises an implementation for each method defined for said abstract class, and wherein said session manager is invoked by invoking a particular method implementation provided by said session manager.

11. The apparatus of claim 7, wherein said associated client requests are associated with each other by way of a session ID.

12. The apparatus of claim 7, wherein determining a session manager to associate with said application comprises:

accessing a set of configuration information which specifies which session manager to associate with said application.

13. A computer readable medium having stored thereon instructions which, when executed by one or more processors, cause the one or more processors to service client requests, said computer readable medium comprising:

instructions for causing one or more processors to receive multiple associated client requests; and

instructions for causing one or more processors to respond to each of said associated client requests by;

invoking an application;

determining, based upon said application, a session manager to associate with said application; and

invoking said session manager to manage state information for said application across said multiple associated client requests.

14. The computer readable medium of claim 13, wherein said session manager is invoked via a programming interface.

15. The computer readable medium of claim 14, wherein said programming interface comprises a definition of an abstract class, and wherein said session manager is a subclass of said abstract class.

16. The computer readable medium of claim 15, wherein said session manager comprises an implementation for each method defined for said abstract class, and wherein said session manager is invoked by invoking a particular method implementation provided by said session manager.

17. The computer readable medium of claim 13, wherein said associated client requests are associated with each other by way of a session ID.

18. The computer readable medium of claim 13, wherein determining a session manager to associate with said application comprises:

accessing a set of configuration information which specifies which session manager to associate with said application.