MAINTAINING SESSIONS IN A SMART THIN CLIENT SERVER

• US 20130041939A1
• Filed: 08/09/2012
• Published: 02/14/2013
• Est. Priority Date: 08/09/2011
• Status: Active Grant

• Current Assignee: MobileFrame LLC
• Original Assignee: MobileFrame LLC
• Inventors: Wickman, Glenn Ward
• Granted Patent: US 9,049,174 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/2895 Intermediate processing functionally located close to the data provider application, e.g. reverse proxies
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

A method for maintaining a session between a smart thin client and a smart thin client server is provided. The smart thin client server permits a user to create, manage, and deploy enterprise applications via the smart thin client but lacks the ability to save state information. The method includes detecting a log-off event for the session between the smart thin client and the smart thin client server; and saving, by the smart thin client server in a database accessible by the smart thin client server, state information for the session, in a record containing a user identification corresponding to a user of the smart thin client.

Claims

1. A method for maintaining a session between a smart thin client and a smart thin client server, the method comprising:

detecting a log-off event for the session between the smart thin client and the smart thin client server, the smart thin client server to permit a user to create, manage, and deploy enterprise applications via the smart thin client but without the ability to save state information; and

saving, by the smart thin client server in a database accessible by the smart thin client server, state information for the session, in a record containing a user identification corresponding to the user of the smart thin client.

2. The method of claim 1, wherein detecting further comprises:

detecting a user explicitly logging off of the session.

3. The method of claim 1, wherein detecting further comprises:

detecting a lack of activity of a user of the smart thin client.

4. The method of claim 1, wherein detecting further comprises:

detecting a shut-down notice from an operating system of the smart thin client.

5. The method of claim 1, wherein detecting further comprises:

detecting an explicit request to log-off from an enterprise application managed by the smart thin client server.

6. The method of claim 1, wherein the state information saved by the smart thin client server is configurable by a user of the smart thin client.

7. The method of claim 1, wherein the state information includes application authoring state and state of variable for data collected by applications managed by the smart thin client server on behalf of the smart thin client.

8. The method of claim 1, wherein the smart thin client is unable to store cookies.

9. The method of claim 1, wherein the state information includes information about what a user has typed on the screen of a computer.

10. A smart thin client server for communication with one or more smart thin clients, the smart thin client server comprising:

a memory to store a web session corresponding to a session between the smart thin client server and the one or more smart thin clients;

a session rendering engine configured to cause the session to be rendered on a smart thin client;

a session manager configured to detect a log-off event for the session, and to save state information for the session, in a record containing a user identification corresponding to the user.

11. The smart thin client server of claim 10, wherein the web session includes:

an application/logic definition;

one or more presentation definitions;

application data; and

web session properties.

12. The smart thin client server of claim 10, wherein detecting includes detecting a user explicitly logging off of the session.

13. The smart thin client server of claim 10, wherein detecting further comprises:

detecting a lack of activity of a user of the smart thin client.

14. The smart thin client server of claim 10, wherein detecting further comprises:

detecting a shut-down notice from an operating system of the smart thin client.

15. The smart thin client server of claim 10, wherein detecting further comprises:

detecting an explicit request to log-off from an enterprise application managed by the smart thin client server.

16. The smart thin client server of claim 10, wherein the state information saved by the smart thin client server is configurable by a user of the smart thin client.

17. The smart thin client server of claim 10, wherein the state information includes application authoring state and state of variable for data collected by applications managed by the smart thin client server on behalf of the smart thin client.

18. The smart thin client server of claim 10, wherein the smart thin client is unable to store cookies.

19. The smart thin client server of claim 10, wherein the state information includes information about what a user has typed on the screen of a computer.

20. A non-transitory computer-readable storage medium storing a set of instructions that, when executed by a processor, cause the processor to perform operations, comprising:

detecting a log-off event for a session between a smart thin client and the smart thin client server, the smart thin client server to permit a user to create, manage, and deploy enterprise applications via the smart thin client but without the ability to save state information; and

saving, by the smart thin client server in a database accessible by the smart thin client server, state information for the session, in a record containing a user identification corresponding to the user of the smart thin client.