Sessions and session states

• US 20070061467A1
• Filed: 09/15/2005
• Published: 03/15/2007
• Est. Priority Date: 09/15/2005
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Levenkov, Alexei, Singh, Balbir, Aggarwal, Ranjan, Leavitt, Adrienne, Essey, Edward
• Application Number:
  US11/227,550
• Publication Number:
  US 20070061467A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70

Abstract

Systems and/or methods (“tools”) are described that enable application-specific session states in a single session, a network entity to be brought down without data loss, additional privacy for session states, continuity when a session state'"'"'s version differs from that of the session state'"'"'s network application, cessation of unnecessary roundtrips attempting to fetch session states, and other techniques. Some of these techniques may be enabled with a data structure having a single binary large object having application-specific identifiers for portions of the binary large object, version identifiers for those portions, a client token indicating the client associated with session states in the binary large object, and a session identifier indicating the session in which these session states exist.

Claims

1. A computer-readable media having a computer-readable data structure, the data structure, when read by a computer, enabling session states for multiple applications or application instances to be accessed as part of a single session, the data structure comprising a single binary large object (BLOB) and two or more application identifiers, each application identifier indicating a portion of the BLOB having a session state for a network-enabled application.

2. The media of claim 1, wherein each application identifier is stored as a namespace in the BLOB.

3. The media of claim 1, the data structure further comprising a session identifier indicating the single session in which the session states are a part.

4. The media of claim 3, the data structure further comprising a client token indicating a user or client associated with the single session.

5. The media of claim 1, wherein the data structure further comprises a version identifier indicating a version of the session state in one of the portions of the BLOB.

6. The media of claim 1, wherein two or more of the application identifiers indicate portions of the BLOB having session states for a same network-enabled application but different instances of the same network-enabled application.

7. The media of claim 1, wherein two or more of the application identifiers indicate portions of the BLOB having session states for different network-enabled applications, each of the different network-enabled applications not capable of understanding the other application'"'"'s session state.

8. The media of claim 1, wherein the BLOB is serialized with the application identifiers.

9. A computer-implemented method comprising:

receiving session information indicating a session between a client and a network-enabled application;

translating the session information to provide translated session information; and

embedding the translated session information into post-back information from the network-enabled application that is intended for use by the client.

10. The method of claim 9, wherein the session information is part of a cookie or universal resource locator and the translated session information is not part of a cookie or universal resource locator.

11. The method of claim 9, wherein the session information comprises a client token associated with the client and capable of differentiating the client from other clients.

12. The method of claim 9, wherein the session information comprises an application identifier associated with the network application and capable of differentiating the network application from other network applications.

13. The method of claim 9, wherein the post-back information comprises view information and the act of embedding embeds the translated session information as a control in the view information.

14. The method of claim 9, further comprising receiving a request from the client having the translated session information and further comprising translating the translated session information to provide second session information in a form interpretable by the network application or a server associated with the network application.

15. A computer-implemented method comprising:

receiving an initial or subsequent request to interact with a network entity, the initial request necessitating a new session with the network entity and the subsequent request not necessitating a new session with the network entity;

determining a state for the network entity;

permitting the initial or subsequent request if the state permits new sessions; and

permitting the request if it is a subsequent request and not permitting the request if it is an initial request if the state permits continuation of exiting sessions but not new sessions.

16. The method of claim 15, further comprising determining whether the state indicates that the network entity does not have any existing sessions and is not accepting any new sessions.

17. The method of claim 16, further comprising bringing the network entity down without loss of a session state.

18. The method of claim 15, wherein the network entity comprises a server.

19. The method of claim 15, wherein the network entity comprises a network-enabled application and the session comprises a session state.

20. The method of claim 15, wherein the network entity comprises an instance of a network-enabled application and the session comprises a session state for the instance.