Session handling
First Claim
Patent Images
1. A method for processing requests in a network having a server and a client, the method comprising:
- in the network, receiving a first request from a user as a first ClientUser request;
receiving subsequent requests from the user as subsequent ClientUser requests;
assigning the first ClientUser request and subsequent ClientUser requests from the user to a ServerSession and associating the ServerSession exclusively with the user, the ServerSession having one or more ClientSessions, the ClientSessions of a ServerSession representing requests from the user associated with the ServerSession;
acquiring a resource;
determining whether either of the ServerSession and one of the ClientSessions has scone and whether the resource should be allocated to either of the ServerSession and one of the ClientSessions;
registering the acquired resource to one of;
(a) the ServerSession or (b) one of the ClientSessions based on the determinations;
releasing the resource when the scope ends; and
receiving the requests by a dispatch servlet running on the server and invoking each request as a thread in a single daemon process.
3 Assignments
0 Petitions
Accused Products
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.
-
Citations
34 Claims
-
1. A method for processing requests in a network having a server and a client, the method comprising:
-
in the network, receiving a first request from a user as a first ClientUser request; receiving subsequent requests from the user as subsequent ClientUser requests; assigning the first ClientUser request and subsequent ClientUser requests from the user to a ServerSession and associating the ServerSession exclusively with the user, the ServerSession having one or more ClientSessions, the ClientSessions of a ServerSession representing requests from the user associated with the ServerSession; acquiring a resource; determining whether either of the ServerSession and one of the ClientSessions has scone and whether the resource should be allocated to either of the ServerSession and one of the ClientSessions; registering the acquired resource to one of;
(a) the ServerSession or (b) one of the ClientSessions based on the determinations;releasing the resource when the scope ends; and receiving the requests by a dispatch servlet running on the server and invoking each request as a thread in a single daemon process. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. A method for processing requests in a network having a server and a client, the method comprising:
-
in the client server network, receiving a first request from a user for an application as a first ClientUser request; receiving subsequent requests from the user as subsequent ClientUser requests; assigning the first ClientUser request and subsequent ClientUser requests from the user to a ServerSession and associating the ServerSession exclusively with the user, the ServerSession having one or more ClientSessions, the ClientSessions of a ServerSession representing requests from the user associated with the ServerSession; displaying a ClientWindow, which is a user interface window that displays all applications requested by the user; displaying an ApplicationWindow, which is a user interface window that displays the application, within the ClientWindow; executing the application in the ApplicationWindow of the ClientWindow; acquiring a resource; determining whether either of the ServerSession and one of the ClientSessions has scone and whether the resource should be allocated to either of the ServerSession and one of the ClientSessions registering the acquired resource to one of;
(a) the ServerSession or (b) one of the ClientSessions based on the determinations; andreleasing the resource when the scone ends; wherein receiving a request comprises receiving the request by a dispatch servlet running on the server, and invoking each request as a thread in a single daemon process. - View Dependent Claims (13, 14, 15, 16, 17)
-
-
18. 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, determining a single application window for execution of applications corresponding to the multiple HTTP requests, acquiring a resource, determining whether either of the ServerSession and one of the ClientSessions has scone and whether the resource should be allocated to either of the ServerSession and one of the ClientSessions, registering the acquired resource to a ServerSession or a ClientSession based on the determinations, and releasing the resource when the scone ends; wherein the requests are received by a dispatch servlet running on the server, and each request is invoked as a thread in a single daemon process. - View Dependent Claims (19, 20, 21)
-
-
22. A computer program product, tangibly embodied in a computer-readable storage medium, the computer program product being operable to cause a data processing apparatus to:
-
receive a first request from a user for an application as a first ClientUser request; receive subsequent requests from the user as subsequent ClientUser requests; assign the first ClientUser request and subsequent ClientUser requests from the same user to a ServerSession and associate the ServerSession exclusively with the user, the ServerSession having one or more ClientSessions, the ClientSessions of a ServerSession representing distinct requests from the user associated with the ServerSession; display a ClientWindow, which is a user interface window that displays all applications requested by the user; display an ApplicationWindow, which is a user interface window that displays the application, within the ClientWindow; execute the application in the ApplicationWindow of the ClientWindow, acquire a resource; determining whether either of the ServerSession and one of the ClientSessions has scope and whether the resource should be allocated to either of the ServerSession and one of the ClientSessions; register the acquired resource to one of;
(a) the ServerSession or (b) one of the ClientSessions based on the determinations; andrelease the resource when the scope ends; wherein the requests are received by a dispatch servlet running on a server, and each request is invoked as a thread in a single daemon process. - View Dependent Claims (23, 24, 25, 26, 27)
-
-
28. A method comprising:
-
in a client/server network, providing a session that is common to all connections to a web server by a user; acquiring a resource; determining whether either of the ServerSession and one of the ClientSessions has scone and whether the resource should be allocated to either of the ServerSession and one of the ClientSessions; registering the acquired resource to a ServerSession or a ClientSession based on the determinations; and releasing the resource when the scone ends; wherein the client sends a request to the web server, the request is received by a dispatch servlet running on the server, and the request is invoked as a thread in a single daemon process. - View Dependent Claims (29, 30, 31, 32, 33, 34)
-
Specification