System and method for managing connections

• US 7,571,236 B2
• Filed: 06/07/2004
• Issued: 08/04/2009
• Est. Priority Date: 06/07/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Jurova, Maria
• Primary Examiner(s): OSMAN, RAMY M
• Application Number:
  US10/863,020
• Publication Number:
  US 20060047755A1
• Time in Patent Office: 1,884 Days
• Field of Search: 709/202, 709/203, 709/217, 709227-229, 709/220, 709223-225
• US Class Current: 709/228
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/563 Data redirection of data network streams

Abstract

Embodiments of the invention are generally directed to a system and method for managing connections. A filter may receive a client request message having one or more parameters. In an embodiment, the filter may modify the request message based, at least in part, on the one or more parameters. The modified request message may indicate that a connection to the client is to remain open after a corresponding response message is sent. In an embodiment, the modified request message is passed to an application for processing.

Claims

1. A method comprising:

receiving from a client, via a connection between the client and a server computer, a request message to exit a service provided by the server and to close the connection to the client;

modifying the request message to indicate that the connection to the client is to remain open after a corresponding response message is sent;

passing the modified request message to an application on the server for processing;

after processing the modified request message, sending the corresponding response message to the client via the connection, wherein the connection to the client is maintained subsequent to sending the response message; and

releasing one or more request processing resources responsive to sending the response message to the client, including

releasing an application thread associated with the service to enable the application to process another request message from the client, and

releasing memory resources associated with processing the request message.

2. The method of claim 1, wherein receiving the request message comprises:

receiving a HyperText Transfer Protocol (HTTP) request from the client.

3. The method of claim 2, wherein modifying the request message comprises:

generating an HTTP request object indicating that the HTTP request object is to be maintained after the response message is sent to the client; and

generating an HTTP response object indicating that the HTTP response object is to be maintained after the response message is sent to the client.

4. The method of claim 3, wherein passing the modified request message to the application for processing comprises:

passing the HTTP request object to the application; and

passing the HTTP response object to the application.

5. The method of claim 1, further comprising

storing the modified request message in memory.

6. The method of claim 5, further comprising:

accessing the modified request message to identify the client; and

sending another response message to the client based, at least in part, on the modified request message.

7. The method of claim 6, further comprising:

receiving an indication that the client has closed the connection; and

releasing one or more connection resources, responsive to receiving the indication that the client has closed the connection.

8. The method of claim 7, wherein receiving the indication that the client has closed the connection comprises at least one of:

receiving an exception responsive to writing to an output stream of the connection to the client;

receiving an exception responsive to reading from an input stream of the connection to the client; and

receiving a closed client connection notification from an event listener.

9. The method of claim 8, wherein releasing one or more connection resources comprises at least one of:

closing an input stream of the connection;

closing an output stream of the connection; and

releasing memory resources associated with processing the request message.

10. The method of claim 1, wherein the application is a Web application.

11. The method of claim 10, wherein the Web application includes at least one of:

a servlet;

a Java Server Page; and

a portlet.

12. A system comprising:

a client; and

a server computer for coupling to the client, the server computer to include

a communication service to receive a request message from the client via a connection between the client and the server computer to exit the communication service and to close the connection to the client, the communication service to further provide a request object based, at least in part, on the received request message,

a filter to receive the request object from the communication service and to generate a modified request object based, at least in part, on the received request object, wherein the modified request object is to indicate that the connection to the client is to be maintained subsequent to sending a corresponding response message, and one or more request processing resources responsive to sending the response message to the client are to be released, and

an application to receive and process the modified request object, and to generate the corresponding response message based, at least in part, on the modified request object after processing the modified request object, wherein the one or more request processing resources responsive to sending the response message to the client include

an application thread associated with the communication service, and

memory resources associated with processing the modified request message.

13. The system of claim 12, wherein

the communication service is a HyperText Transfer Protocol (HTTP) service;

the received request message is an HTTP request message;

the request object is an HTTP request object; and

the modified request object is a modified HTTP request object.

14. The system of claim 12, wherein the modified request object further indicates that the modified request object is to be maintained subsequent to sending the response message to the client.

15. The system of claim 14, wherein the modified request object is to be stored in memory.

16. The system of claim 15, wherein the application is to generate another response message based, at least in part, on the modified request object.

17. The system of claim 12, the server to further include an event listener to notify the application if the client closes the connection.

18. An article of manufacture comprising a computer-readable storage medium having instructions stored thereon to cause a processor to perform operations including:

receiving from a client, via a connection between the client and a server computer, a request message to exit a service provide by the server and to close the connection to the client;

modifying the request message to indicate that the connection to the client is to remain open after a corresponding response message is sent;

passing the modified request message to an application on the server for processing;

after processing the modified request message, sending the corresponding response message to the client via the connection, wherein the connection to the client is maintained subsequent to sending the response message; and

releasing one or more request processing resources responsive to sending the response message to the client, including

releasing an application thread associated with the service to enable the application to process another request message, from the client, and

releasing memory resources associated with processing the request message.

19. The article of manufacture of claim 18, wherein receiving the request message further includes:

receiving a HyperText Transfer Protocol (HTTP) request from the client.

20. The article of manufacture of claim 19, wherein modifying the request message further includes:

generating an HTTP request object indicating that the HTTP request object is to be maintained after the response message is sent to the client; and

generating an HTTP response object indicating that the HTTP response object is to be maintained after the response message is sent to the client.

21. The article of manufacture of claim 18, further including storing the modified request message in memory.

22. The article of manufacture of claim 21, further including

accessing the modified request message to identify the client;

and

sending another response message to the client based, at least in part, on the modified request message.

23. The article of manufacture of claim 22, further including

receiving an indication that the client has closed the connection;

and

releasing one or more connection resources, response to receiving the indication that the client has closed the connection.