Techniques for increasing efficiency while servicing requests for database services

• US 6,950,822 B1
• Filed: 11/25/2002
• Issued: 09/27/2005
• Est. Priority Date: 11/06/2002
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Sedlar, Eric, Idicula, Sam, Murthy, Ravi, Agarwal, Nipun
• Primary Examiner(s): Mizrahi, Diane D.
• Application Number:
  US10/304,478
• Time in Patent Office: 1,037 Days
• Field of Search: 707 1- 10, 707100-1041, 707200-205, 709/203, 709/206, 709/227, 713/127, 713/130, 713/170, 713/185, 713/201, 717/127, 717/130, 380/37
• US Class Current: 1/1
• 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

Techniques for servicing requests for database services include maintaining at a database server an available set of one or more database session data structures. Each database session data structure holds information to support one session of one or more requests for database services over a communication connection that persists for one or more communications from one client. A database session data structure in the available set is not associated with any client currently connected to the database server. These techniques allow a database server to more efficiently service more numerous requests for database services, such as generated by communications using a stateless protocol like HTTP.

Claims

1. A computer-implemented method for servicing requests for database services, the method comprising the step of:

creating at a database server an available set of one or more database session data structures,

wherein

each database session data structure holds information to support one session of one or more requests for database services over a communication connection that persists for one or more communications from one client, and

a database session data structure in the available set is not associated with any client currently connected to the database server.

2. The method of claim 1, further comprising the steps of:

receiving, from a client, a request that opens a session;

removing a particular database session data structure from the available set; and

associating the particular database session data structure with the client.

3. The method of claim 2, wherein:

the method further comprises the step of determining whether the database server has an available set; and

said steps of removing the particular database session data structure and associating the particular database session data structure with the client are performed only if it is determined that the database server has an available set.

4. The method of claim 3, further comprising, if it is determined that the database server does not have an available set, then performing the steps of:

creating a new database session data structure; and

associating the new database session data structure with the client.

5. The method of claim 2, said step of receiving the request comprising the step of receiving a stateless request that establishes a communication connection that persists for no more than one communication from a particular client.

6. The method of claim 5, wherein the stateless request is one of a hypertext transfer protocol (HTTP) request and a web-based distributed authoring and versioning (WebDAV) request that extends HTTP.

7. The method of claim 1, further comprising

terminating a session with a client that is associated with a particular database session data structure;

and

adding the particular database session data structure to the available set.

8. The method of claim 7, said step of adding the particular database session data structure further comprising the step of removing an association between the particular database session data structure and the client.

9. The method of claim 7, said step of adding the particular database session data structure further comprising the steps of:

determining whether the database server has an available set; and

if the database server does not have an available set, then creating an available set with the particular database session data structure.

10. The method of claim 7, wherein:

the method further comprises the step of determining whether the available set has a maximum number of database session data structures; and

said step of adding the particular database session data structure to the available set is performed only if it is determined that the available set has less than the maximum number of database session data structures.

11. The method of claim 7, further comprising, if it is determined that the available set has a maximum number of database session data structures, then performing the step of releasing the particular database session data structure.

12. The method of claim 7, said step of terminating the request comprising the step of sending a response to a stateless request that establishes a communication connection that persists for no more than one communication from a particular client.

13. The method of claim 12, wherein the stateless request is one of a hypertext transfer protocol (HTTP) request and a web-based distributed authoring and versioning (WebDAV) request that extends HTTP.

14. The method of claim 1, said step of maintaining the available set further comprising the step of establishing an available set data structure that holds data that indicates:

a number of zero or more database session data structures that are not associated with any client; and

one or more properties for each of the number of the database session data structures that are not associated with any client.

15. A computer-readable medium carrying one or more sequences of instructions for servicing requests for database services, wherein execution of the one or more sequences of instructions by one or more processors causes the one or more processors to perform the step of:

creating at a database server an available set of one or more database session data structures,

wherein

each database session data structure holds information to support one session of one or more requests for database services over a communication connection that persists for one or more communications from one client, and

a database session data structure in the available set is not associated with any client currently connected to the database server.

16. The computer-readable medium of claim 15, wherein execution of the one or more sequences of instructions further causes the one or more processors to perform the steps of:

receiving a request from a client to open a session;

removing a particular database session data structure from the available set; and

associating the particular database session data structure with the client.

17. The computer-readable medium of claim 16, wherein:

execution of the one or more sequences of instructions further causes the one or more processors to perform the step of determining whether the database server has an available set; and

said steps of removing the particular database session data structure and associating the particular database session data structure with the client are performed only if it is determined that the database server has an available set.

18. The computer-readable medium of claim 17, wherein execution of the one or more sequences of instructions further causes the one or more processors, if it is determined that the database server does not have an available set, to perform the steps of:

creating a new database session data structure; and

associating the new database session data structure with the client.

19. The computer-readable medium of claim 16, said step of receiving the request comprising the step of receiving a stateless request that establishes a communication connection that persists for no more than one communication from a particular client.

20. The computer-readable medium of claim 19, wherein the stateless request is one of a hypertext transfer protocol (HTTP) request and a web-based distributed authoring and versioning (WebDAV) request that extends HTTP.

21. The computer-readable medium of claim 15, wherein execution of the one or more sequences of instructions further causes the one or more processors to perform the steps of:

terminating a session with a client that is associated with a particular database session data structure; and

adding the particular database session data structure to the available set.

22. The computer-readable medium of claim 21, said step of adding the particular database session data structure further comprising the step of removing an association between the particular database session data structure and the client.

23. The computer-readable medium of claim 21, said step of adding the particular database session data structure further comprising the steps of:

determining whether the database server has an available set; and

if the database server does not have an available set, then creating an available set with the particular database session data structure.

24. The computer-readable medium of claim 21, wherein:

execution of the one or more sequences of instructions further causes the one or more processors to perform the step of determining whether the available set has a maximum number of database session data structures; and

said step of adding the particular database session data structure to the available set is performed only if it is determined that the available set has less than the maximum number of database session data structures.

25. The computer-readable medium of claim 21, wherein execution of the one or more sequences of instructions further causes the one or more processors, if it is determined that the available set has a maximum number of database session data structures, to perform the step of releasing the particular database session data structure.

26. The computer-readable medium of claim 21, said step of terminating the request comprising the step of sending a response to a stateless request that establishes a communication connection that persists for no more than one communication from a particular client.

27. The computer-readable medium of claim 26, wherein the stateless request is one of a hypertext transfer protocol (HTTP) request and a web-based distributed authoring and versioning (WebDAV) request that extends HTTP.

28. The computer-readable medium of claim 15, said step of maintaining the available set further comprising the step of establishing an available set data structure that holds data that indicates:

a number of zero or more database session data structures that are not associated with any client; and

one or more properties for each of the number of the database session data structures that are not associated with any client.