SHARING THE COMMON SESSION BETWEEN TWO APPLICATIONS ON THE SAME SERVER

• US 20080282258A1
• Filed: 05/08/2008
• Published: 11/13/2008
• Est. Priority Date: 05/10/2007
• Status: Abandoned Application

• Current Assignee: Blackberry Limited
• Original Assignee: Blackberry Limited
• Inventors: MADEJ, Piotr
• Application Number:
  US12/117,260
• Publication Number:
  US 20080282258A1
• Time in Patent Office: Days
• US Class Current: 719/313
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

Abstract

A method of automatically sharing session data between two or more applications executing on a common server. Each application has a respective session. A copy of all session data of a first application'"'"'s session is stored in a servlet context resident on the server. The stored session data is copied to a second application'"'"'s session. Thereafter, the stored session data is deleted.

Claims

1. A method of automatically sharing session data between two or more applications executing on a common server, each application having a respective session, the method comprising steps of:

storing a copy of all session data of a first application'"'"'s session in a servlet context resident on the server;

copying the stored session data to a second application'"'"'s session on the server; and

thereafter deleting the stored session data.

2. A method as claimed in claim 1, wherein the step of storing a copy of session data of the first application'"'"'s session comprises steps of:

selecting a unique key in respect of the first application'"'"'s session; and

storing the session data in an entry of the servlet context, associated with the selected key.

3. A method as claimed in claim 2, wherein the unique key corresponds with a session key of the first application'"'"'s session and the session key is included in a link used to access the second application from the first application.

4. A method as claimed in claim 1, wherein the servlet context is instantiated by a redirector servlet executing on the server to enable interaction between at least the first and second applications.

5. A method as claimed in claim 1, wherein the step of storing a copy of session data of the first application'"'"'s session comprises storing the entire session of the first application.

6. A method as claimed in claim 1, wherein the step of storing a copy of session data of the first application'"'"'s session comprises storing a predetermined portion of the session of the first application.

7. A method as claimed in claim 6, wherein the predetermined portion of the session of the first application comprises all session data associated with the session including any one or more of:

user login;

user authentication;

user information;

user account information;

payment information; and

role management information.

8. A server comprising:

a processor for controlling operation of the server;

a first input device coupled to the processor for accepting an input;

a communications subsystem coupled to the processor for communicating with a communications network;

a memory coupled to the processor; and

a storage device coupled to the processor;

the server including a software module resident in the memory for execution by the processor, the software module for automatically sharing session data between two or more applications executing on the server, each application having a respective session, the software module being configured to;

store a copy of all session data of a first application'"'"'s session in a servlet context resident on the server;

copy the stored session data to a second application'"'"'s session on the server; and

thereafter delete the stored session data.

9. The server as claimed in claim 8, wherein the storing a copy of session data of the first application'"'"'s session comprises:

selecting a unique key in respect of the first application'"'"'s session; and

storing the session data in an entry of the servlet context, associated with the selected key.

10. The server as claimed in claim 9, wherein the unique key corresponds with a session key of the first application'"'"'s session and the session key is included in a link used to access the second application from the first application.

11. The server as claimed in claim 8, wherein the servlet context is instantiated by a redirector servlet executing on the server to enable interaction between at least the first and second applications.

12. The server as claimed in claim 8, wherein the storing a copy of session data of the first application'"'"'s session comprises storing the entire session of the first application.

13. The server as claimed in claim 8, wherein the step of storing a copy of session data of the first application'"'"'s session comprises storing a predetermined portion of the session of the first application.

14. The server as claimed in claim 13, wherein the predetermined portion of the session of the first application comprises all session data associated with the session including any one or more of:

user login;

user authentication;

user information;

user account information;

payment information; and

role management information