Session handling

• US 20050050204A1
• Filed: 09/02/2003
• Published: 03/03/2005
• Est. Priority Date: 09/02/2003
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Cherdron, Markus, Beck, Stefan, Singler, Joerg
• Granted Patent: US 7,664,860 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• 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 includes, in a network, representing a first request from a first user as a first ClientUser, assigning the first ClientUser to a ServerSession, the ServerSession having one or more ClientSessions, each of the ClientSessions allowing a server to have a single session for all first user requests from the server. The method includes, in a client/server network, providing a session that can be common to all connections to a web server by a user.

Claims

1. A method comprising:

in a network, representing a first request from a first user as a first ClientUser; and

assigning the first ClientUser to a ServerSession, the ServerSession having one or more ClientSessions, each of the ClientSessions allowing a server to have a single session for all first user requests from the server.

2. The method of claim 1 in which each of the ClientSessions represent an abstraction of an HTTP session unbound from hypertext transfer protocol (HTTP) peculiarities.

3. The method of claim 1 further comprising:

receiving a second request from the first user as a second ClientUser; and

assigning the second ClientUser to the ServerSession.

4. The method of claim 1 in which the server is a web server.

5. The method of claim 4 in the first ClientUser is a client using a stateless protocol.

6. The method of claim 4 in which the stateless protocol is hypertext transfer protocol (HTTP).

7. The method of claim 1 further comprising displaying a first application requested by the first user and associated with a first ClientApplication in a ClientWindow.

8. The method of claim 7 further comprising displaying a second application requested by the first user and associated with a second ClientApplication in the ClientWindow.

9. The method of claim 8 further comprising displaying a third application requested by the first user and associated with a third ClientApplication in the ClientWindow.

10. The method of claim 1 further comprising alternately displaying ClientApplications in a single ClientWindow.

11. A method comprising:

in a client server network, receiving a request for an application;

obtaining a ClientSession;

obtaining a ClientWindow;

obtaining an ApplicationWindow; and

executing the application in the application window of the ClientWindow.

12. The method of claim 11 in which the request is a hypertext transfer protocol (HTTP) request.

13. The method of claim 11 in which the ClientSession is a hypertext transfer protocol (HTTP) session.

14. The method of claim 11 in which the ClientWindow represents a client session.

15. The method of claim 11 in which the ApplicationWindow is a-client window.

16. A network comprising:

a browser client device; and

a client manager residing in a server for receiving multiple hypertext transfer protocol (HTTP) requests from the browser client device and determining a single application window for execution of applications corresponding to the multiple HTTP requests.

17. The network of claim 16 in which the client manager includes a servlet.

18. The network of claim 16 in which the client manager establishes client session, a single server session, a client window and an application window in response to the multiple requests from the browser client device.

19. The network of claim 18 in which the client session is a hypertext transfer protocol (HTTP) session.

20. A computer program product, tangibly embodied in an information carrier, the computer program product being operable to cause data processing apparatus to:

receiving a request for an application;

obtain a ClientSession;

obtain a ClientWindow;

obtain an ApplicationWindow; and

execute the application in the application window of the ClientWindow.

21. The product of claim 20 in which the request is a hypertext transfer protocol (HTTP) request.

22. The product of claim 20 in which the ClientSession is a hypertext transfer protocol (HTTP) session.

23. The product of claim 20 in which the ClientWindow represents a client session.

24. The product of claim 20 in which the ApplicationWindow is a client window.

25. A method comprising:

in a client/server network, providing a session that is common to all connections to a web server by a user.

26. The method of claim 25 in which the connections are different browser processes.

27. The method of claim 25 in which the connections are different browsers.

28. The method of claim 25 in which the connections are different client devices.

29. The method of claim 25 in which the user is a client using a stateless protocol.

30. The method of claim 29 in which the stateless protocol is hypertext markup language (HTML) protocol.