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.
2. The method of claim 1 in which the ClientSessions represent abstractions of HTTP sessions.
3. The method of claim 1 further comprising:
receiving a second request from the first user as a second ClientUser request; and
assigning the second ClientUser request to the ServerSession.
4. The method of claim 1 in which the server is a web server.
5. The method of claim 4 in which the first ClientUser request is from a client using a stateless protocol.
6. The method of claim 5 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 user in a ClientWindow, which is a user interface window that displays all applications requested by the user.
8. The method of claim 7 further comprising displaying a second application requested by the user in the ClientWindow.
9. The method of claim 8 further comprising displaying a third application requested by the user in the ClientWindow.
10. The method of claim 1 further comprising alternately displaying applications requested by the user in a single ClientWindow, which is a user interface window that displays all applications requested by the user.
11. The method of claim 1 further comprising releasing the acquired resource registered to the one or more ClientSessions upon termination of the one or more ClientSessions.
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; and
releasing 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.
13. The method of claim 12 in which the requests are hypertext transfer protocol (HTTP) requests.
14. The method of claim 12 in which the ClientSession is a hypertext transfer protocol (HTTP) session.
15. The method of claim 12 in which the ClientWindow represents a client session.
16. The method of claim 12 in which the ApplicationWindow is a client window.
17. The method of claim 12 further comprising releasing the acquired resource registered to the one or more ClientSessions upon termination of the one or more ClientSessions.
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.
19. The network of claim 18 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.
20. The network of claim 19 in which the client session is a hypertext transfer protocol (HTTP) session.
21. The network of claim 18 in which the client manager releases the acquired resource registered to the one or more ClientSessions upon termination of the one or more ClientSessions.
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; and
release 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.
23. The product of claim 22 in which the requests are hypertext transfer protocol (HTTP) requests.
24. The product of claim 22 in which the ClientSessions are hypertext transfer protocol (HTTP) sessions.
25. The product of claim 22 in which the ClientWindow represents a client session.
26. The product of claim 22 in which the ApplicationWindow is a client window.
27. The product of claim 22 further being operable to cause a data processing apparatus to release the acquired resource registered to the one or more ClientSessions upon termination of the one or more ClientSessions.
28. A method comprising:
in a clientserver 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.
29. The method of claim 28 in which the connections are different browser processes.
30. The method of claim 28 in which the connections are different browsers.
31. The method of claim 28 in which the connections are different client devices.
32. The method of claim 28 in which the user is a client using a stateless protocol.
33. The method of claim 32 in which the stateless protocol is hypertext markup language (HTML) protocol.
34. The method of claim 28 further comprising releasing the acquired resource registered to the one or more ClientSessions upon termination of the one or more ClientSessions.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A machine comprising:
a chassis;
an operator cab;
an engine;
a radiator;
a hood assembly including an engine hood being moveably mounted with respect to the chassis, and a radiator hood being moveably mounted with respect to the chassis, said hood assembly being characterized by three configurations including a fully closed configuration, a fully open configuration, and a radiator hood open configuration;
wherein said radiator hood twice intersects a transversely oriented line passing between the engine and the radiator in at least one of the three configurations and does not intersect the line in at least one other of the three configurations; wherein the radiator hood opens in one direction into the radiator hood open configuration and the radiator hood and engine hood open together in the opposite direction into the fully open configuration; and wherein
the engine and the radiator are rearward of the operator cab.
2. The machine of claim 1, further comprising a first hinge operatively connecting the engine hood and the radiator hood to the chassis and about which the engine hood and radiator hood are selectively rotatable together with respect to the chassis and the operator cab.
3. The machine of claim 2, further comprising a second hinge located forward of the radiator, and operatively connecting the radiator hood to the engine hood and about which the radiator hood is selectively rotatable with respect to the engine hood.
4. The machine of claim 3, wherein the first hinge defines a first axis of rotation about which the radiator hood and the engine hood are selectively rotatable; wherein the second hinge defines a second axis of rotation about which the radiator hood is selectively rotatable; and wherein the first axis and the second axis are substantially parallel to one another.
5. The machine of claim 4, wherein each of the engine hood and the radiator hood is characterized by an inverted U-shaped cross section.
6. The machine of claim 5, further comprising at least one load assist mechanism operatively connected to the radiator hood to selectively urge the radiator hood to rotate about the second axis.
7. The machine of claim 6, further comprising an actuator operatively connected to the engine hood and the radiator hood and configured to selectively rotate the engine hood and the radiator hood together about the first axis.
8. The machine of claim 7, wherein the radiator hood is selectively rotatable about the second axis between a closed position with respect to the engine hood, an open position with respect to the engine hood, and a predetermined bias neutral position that is between the open and closed positions; and wherein said at least one load assist mechanism is sufficiently positioned with respect to the radiator hood to bias the radiator hood toward the closed position when the radiator hood is between the closed position and the bias neutral position, and to bias the radiator hood toward the open position when the radiator hood is between the bias neutral position and the open position.
9. The machine of claim 8, wherein the hood assembly further includes a frame mounted with respect to the engine hood; wherein the first hinge operatively connects the frame to the chassis; and wherein the second hinge operatively connects the radiator hood to the frame.
10. The machine of claim 3 wherein the first hinge is located rearward of the radiator, the engine and the operator cab.
11. The machine of claim 10 wherein the chassis is a wheel loader chassis; and
an implement bucket attached forward of the operator cab.
12. The machine of claim 5 wherein the radiator hood includes a top panel and two side panels that each defines a plurality of holes therethrough.
13. A wheel loader machine comprising:
a chassis;
an operator cab mounted on the chassis;
an engine mounted on the chassis rearward of the operator cab;
a radiator positioned rearward of the engine;
a first hood;
a second hood;
a first hinge defining a first axis and operatively interconnecting the first hood and the second hood such that the second hood is selectively rotatable with respect to the first hood about the first axis; at least
part of a second hinge defining a second axis that is substantially parallel to the first axis such that the first and second hoods are selectively rotatable together about the second axis with respect to the engine, the radiator and the operator cab; and wherein the second hood twice intersects a transversely oriented line passing between the engine and the radiator when in a closed position.
14. The wheel loader machine of claim 13, further comprising a frame mounted with respect to the first hood; wherein the first hinge operatively interconnects the second hood and the frame such that the second hood is selectively rotatable with respect to the frame; and wherein said at least part of a second hinge is operatively connected to the frame such that the frame is selectively rotatable with the first and second hoods about the second axis;
each of the first and second hoods is characterized by a U-shaped cross section; and
the second hood includes a radiator grill.
15. The wheel loader machine of claim 14, further comprising at least one load assist mechanism operatively connected to the second hood to selectively urge the second hood to rotate about the first axis; and
wherein the second hood is selectively rotatable about the first axis between the closed position with respect to the first hood, an open position with respect to the first hood, and a predetermined bias neutral position that is between the open and closed positions; and wherein said at least one load assist mechanism is sufficiently positioned with respect to the second hood to bias the second hood toward the closed position when the second hood is between the closed position and the bias neutral position, and to bias the second hood toward the open position when the second hood is between the bias neutral position and the open position.
16. The wheel loader machine of claim 15, further comprising an actuator operatively coupled to said at least part of a second hinge.