Deterministic session state management within a global cache array

• US 20060155857A1
• Filed: 01/06/2005
• Published: 07/13/2006
• Est. Priority Date: 01/06/2005
• Status: Abandoned Application

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Feenan, James J. Jr., Lei, Ming, Ling, Gary
• Application Number:
  US11/030,528
• Publication Number:
  US 20060155857A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1027 Persistence of sessions during load balancing
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer

Abstract

The present invention is directed to binding a user session in an application to a particular coordination point. The method includes recognizing a defined application session in response to an application generated by a cache. A user session and an origin server that generated the response are bound in a session cookie. Subsequent requests are routed to the same origin server that served the application content for each unique user session based on the session cookie.

Claims

1. A method of binding a user session in an application to an origin server comprising:

recognizing a defined session;

binding a user session and an origin server of the defined session in a session cookie; and

routing subsequent requests for the user session to a same origin server for each user session based on information stored in the session cookie.

2. The method of claim 1 wherein a session definition of the defined session includes a unique session name.

3. The method of claim 2 further comprising configuring a session tracking cookie within a cache that routed an initial request for the session to the origin server, that includes a unique session name included in the session definition, and appending the session tracking cookie to an application cookie returned from the origin server.

4. The method of claim 1 further comprising:

defining in an initial request for a defined session, a unique session name in a cookie or embedded URL parameter that is returned to the user; and

consecutively routing subsequent requests from the user for the defined session to the same origin server to allow stateful request routing for the subsequent requests based on the cookie.

5. The method of claim 3 wherein the session tracking cookie includes a global cache identification for the request across a loosely coupled array of caches in order to bind the session to the origin server.

6. The method of claim 1 further comprising:

receiving a subsequent request from the user for the defined session;

determining a session identifier from the session cookie forwarded by the user with the subsequent request;

updating a session timeout value from the session cookie; and

connecting with the origin server associated with the user session if the defined session is valid.

7. The method of claim 1 wherein the session cookie is formatted to include:

an identity of the origin server;

a unique identifier for a loosely coupled array of caches that handled an initial request for the user session; and

a timeout value of the defined session.

8. The method of claim 1 further comprising configuring the session cookie to include:

a routing path identifier including an identity of a handling cache and the origin server; and

a session identifier generated by the origin server that uniquely identifies the user session associated with a user.

9. The method of claim 8 further comprising including in the session cookie an identifier of a location of an origin server to which an initial request to establish the user session was transmitted.

10. A method of maintaining a session state in a loosely coupled array of caches comprising:

receiving in a cache in the array of caches a first request from a client for a session with an application on a website;

transmitting the first request to an origin server that generates a content of the application from the website and receives an application generated response that includes a value that identifies the session; and

after receiving the application and application generated response in the cache, recognizing that this is a session for a particular site, generating a session cookie in the cache identifying the origin server associated with the first request, the application associated with the first request and a configured timeout, wherein a subsequent non-cached request from the client will be forwarded to the origin server and maintain session information without establishing a new session.

11. The method of claim 10 further comprising:

receiving a subsequent login request from the client for a second application on the website;

transmitting the subsequent request to a corresponding origin server;

the webcache generating another session cookie after receiving an application generated response from the second application that binds the subsequent login to the second application to the corresponding origin server.

12. The method of claim 10 further comprising using load balancing to determine which second origin server to send the second request to.

13. A method of binding a user session in an application to a coordination point for affinity of future requests comprising:

after establishing an initial session with an origin server, tagging a session identification cookie with information identifying the cookie as pertaining to a particular user and the particular user'"'"'s session in an application;

identifying, from the information in the session identification cookie, as an application session to be tracked; and

appending a session tracking cookie that identifies the origin server as handling all requests by the particular user for the application session and a cache array that made an initial decision to establish a connection with the origin server.

14. The method of claim 13 further comprising routing the session identification cookie and the session tracking cookie to the particular user for storage.

15. The method of claim 13 further comprising, in a subsequent request for the application from the particular user, sending the session identification cookie and the session tracking cookie to a cache array wherein the receiving cache receiving the subsequent request identifies a binding decision between the particular user and the application session and sends the subsequent request to the origin server.

16. A method of cookie based session tracking in a loosely coupled cache array comprising:

recognizing a user session;

binding a request associated with the user session to a origin server;

returning a cookie/URL from the origin server to the cache in response to the request;

inserting the origin server binding information into a memory session table; and

using the table to determine an origin server for subsequent requests.

17. The method of claim 16 further comprising, in response to a subsequent request, identifying the subsequent request as a request for a session by the cookie, identifying the session in the cookie from a session identifier in the cookie, and routing the subsequent request to the origin server identified in the cookie.

18. A computer program product comprising:

a computer useable medium having computer readable code means embodied therein for causing a computer to bind a user session in an application to an origin server, the computer readable code means in the computer program product comprising;

computer readable program code means for causing a computer to recognize a defined session;

computer readable program code means for causing a computer to bind the defined session and an origin server that generated a response to the defined session in a session cookie;

computer readable program code means for causing a computer to route subsequent requests for the defined session to the origin server that served the defined session for each unique user session based on the session cookie.