Method and apparatus for implementing recursive remote procedure calls

• US 20060136431A1
• Filed: 12/17/2004
• Published: 06/22/2006
• Est. Priority Date: 12/17/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Dittmar, Daniel
• Granted Patent: US 7,519,601 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/24547 Optimisations to support specific applications; Extensibility of optimisers
• CPC Class Codes: G06F 16/24566 Recursive queries
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99939 Privileged access

Abstract

A system, method, apparatus, means and computer program code for operating a database server are provided including receiving a database request message, the database request message including a user-defined extension (UDE) portion to be processed by a UDE server, transmitting a procedure request to the UDE server based on the UDE portion of the database request message, and determining if a response received from the UDE server is a reply to the procedure request before closing a call stack associated with the database request message.

Claims

1. A method for operating a database server, the method comprising:

receiving a database request message, the database request message including a user-defined extension (UDE) portion to be processed by a UDE server;

transmitting a procedure request to the UDE server based on the UDE portion of the database request message; and

determining if a response received from the UDE server is a reply to the procedure request before closing a call stack associated with the database request message.

2. The method of claim 1, further comprising:

receiving an intermediate message from the UDE server;

determining that the intermediate message is not a reply to the procedure request; and

recursively processing the intermediate message without creating a new call stack.

3. The method of claim 1, wherein the procedure request is formatted in a data packet including a tag.

4. The method of claim 1, wherein the determining indicates that the response is a reply to the procedure request, the determining further comprising:

determining that said response is a procedure reply message, based on a tag associated with said response; and

determining that the procedure request is the next procedure request on said call stack.

5. The method of claim 1, further comprising:

generating a response to the database request message, the response based on the reply.

6. The method of claim 1, further comprising:

transmitting a response to the database request to a client device, the response based on the procedure reply.

7. The method of claim 1, further comprising:

determining that the procedure reply is not a complete reply;

8. The method of claim 2, wherein the determining that the intermediate message is not a reply further comprises:

identifying a tag associated with the intermediate message; and

determining that the intermediate message is not a procedure reply message.

9. The method of claim 8, wherein the determining that the intermediate message is not a procedure reply message further comprises:

determining that the procedure request is not the next procedure in the call stack.

10. The method of claim 8, wherein the data packet includes a SQL database request and the recursively processing includes processing the SQL database request.

11. The method of claim 10, wherein the SQL database request causes the database server to transmit a further procedure request to the UDE server, the further procedure request transmitted without creating a new call stack.

12. A database system, comprising:

a memory storing processor-executable process steps;

an interface for receiving a database request message from a client device; and

at least a first processor in communication with the memory and operative in conjunction with the stored process steps to;

process the database request message to identify a user-defined extension (UDE) portion to be processed by a UDE server;

establish a call stack to track a procedure request based on the UDE portion;

transmit the procedure request to the UDE server; and

determine if a response received from the UDE server is a reply to the procedure request before closing a call stack associated with the database request message.

13. The database system of claim 12, wherein the at least first processor is further operative in conjunction with the stored process steps to:

receive an intermediate message from the UDE server;

determine that the intermediate message is not a reply to the procedure request; and

recursively process the intermediate message without creating a new call stack.

14. The database system of claim 12, wherein the at least first processor is further operative in conjunction with the stored process steps to:

establish a second call stack associated with processing the procedure request by the UDE server;

process the procedure request by the UDE server; and

close the second call stack upon completion of processing the procedure request by the UDE server.

15. The database system of claim 13, wherein the at least first processor is further operative in conjunction with the stored process steps to:

identify a SQL database request in the intermediate message, wherein the recursive process includes recursively processing the SQL database request.

16. A medium storing processor-executable process steps, the process steps comprising:

a step to process a database request message to identify a user-defined extension (UDE) portion to be processed by a UDE server;

a step to establish a call stack to track a procedure request based on the UDE portion;

a step to transmit the procedure request to the UDE server; and

a step to determine if a response received from the UDE server is a reply to the procedure request before closing a call stack associated with the database request message.

17. A medium according to claim 16, the process steps further comprising:

a step to receive an intermediate message from the UDE server;

a step to determine that the intermediate message is not a reply to the procedure request; and

a step to recursively process the intermediate message without creating a new call stack.

18. A medium according to claim 16, the process steps further comprising:

a step to establish a second call stack associated with processing the procedure request by the UDE server;

a step to process the procedure request by the UDE server; and

a step to close the second call stack upon completion of processing the procedure request by the UDE server.

19. A system, comprising:

a client device;

a database server, in communication with the client device to receive a database request message and to transmit a response to the database request message; and

a UDE server, in communication with the database server to receive a procedure request based on a UDE portion of the database request message and to transmit a reply message to the database server, the database server determining if the reply message is a reply to the procedure request by identifying the reply message as a procedure reply and by determining that the procedure request is the next open procedure in a call stack of the database server.