Calling a second functionality by a first functionality

• US 8,266,631 B1
• Filed: 10/28/2004
• Issued: 09/11/2012
• Est. Priority Date: 10/28/2004
• Status: Active Grant

• Current Assignee: Callahan Cellular LLC (Intellectual Ventures LLC)
• Original Assignee: Curen Software Enterprises LLC (Intellectual Ventures LLC)
• Inventors: Wheeler, Thomas T.
• Primary Examiner(s): Anya, Charles E
• Application Number:
  US10/975,827
• Time in Patent Office: 2,875 Days
• Field of Search: 709/201, 709/217, 709/231, 709/203, 709/227, 709/230, 719/315, 719/316, 719/328, 719/330, 719/313
• US Class Current: 719/313
• CPC Class Codes: G06F 9/449 Object-oriented method invocation or resolution
• CPC Class Codes: G06F 9/54 Interprogram communication

Abstract

A method, system, and computer readable medium for calling a second functionality by a first functionality comprises calling a third functionality by the first functionality, wherein the calling includes passing arguments to the third functionality, calling a fourth functionality by the third functionality, wherein the calling includes passing the arguments to the fourth functionality, calling a fifth functionality via the fourth functionality, wherein the calling includes marshalling a request related to the arguments and passing the marshaled request to the fifth functionality, calling a sixth functionality via the fifth functionality, wherein the calling includes unmarshalling the marshaled request, calling the second functionality by the sixth functionality, wherein the calling includes passing the arguments related to the unmarshalled request to the second functionality, returning a response related to the arguments by the second functionality to the fifth functionality via the sixth functionality, calling the fourth functionality by the fifth functionality, wherein the calling includes marshalling the response and passing the marshaled response to the fourth functionality, returning a reply to the third functionality by the fourth functionality, wherein the reply includes unmarshalling the marshaled response, and returning the unmarshalled response to the first functionality by the third functionality.

Claims

1. A method comprising:

receiving an incoming call, with a request manager, from an entity, wherein the incoming call includes a marshaled request related to arguments associated with a different call from a client business object to a proxy object and wherein the request manager is associated with a connection;

querying one or more request handlers as to the respective abilities of the one or more request handlers to process the incoming call, wherein the one or more request handler comprise an Internal Routing Message Protocol (Irmp) request handler;

passing the connection from the request manager associated with the connection to a request handler of the one or more request handlers, wherein the request handler is configured to read data off the connection;

processing the call with the request handler;

calling an adapter via the request handler, wherein calling the adapter includes unmarshalling the marshaled request;

calling a server business object via the adapter effective to pass the arguments associated with the different call to the server business object, wherein the server business object includes at least one operation, and wherein the adapter is configured to call the server business object by mapping a name of the at least one operation to an associated operation;

receiving, with the request handler, a response from the server business object via the adapter; and

calling, with the request handler, the entity effective to marshal the response and pass the marshaled response to the entity, effective to cause a reply including an unmarshalled marshaled response to be returned to the proxy object, and effective to cause a reply including the unmarshalled marshaled response to be returned to the client business object.

2. The method of claim 1, wherein the incoming call includes a marshaled request that further includes at least one of the arguments or an identifier associated with the adapter and an Object Request Broker (ORB) server.

3. The method of claim 2, further comprising passing the marshaled request and the unmarshalled marshaled response according to a specific protocol.

4. The method of claim 1, wherein the incoming call includes a marshaled request that further includes the arguments and an identifier associated with the adapter and an Object Request Broker (ORB) server.

5. The method of claim 4 further comprising:

using, with the ORB server, the identifier to look up the adapter; and

using an acquired connection with the entity to pass the marshaled request and the unmarshalled marshaled response.

6. The method of claim 5, wherein using the acquired connection includes using a connection that is based on information contained in the proxy object.

7. The method of claim 6, wherein the information contained in the proxy object comprises a Universal Resource Locator (URL).

8. The method of claim 1, further comprising binding the adapter within a naming service.

9. The method of claim 8, wherein binding the adapter includes associating the adapter to a Universal Resource Locator (URL) within the naming service.

10. The method of claim 1, wherein the adapter comprises an instance of a class.

11. A method comprising:

receiving a marshaled request from an entity, wherein the request is received with a request manager associated with a connection;

querying one or more request handlers as to the respective abilities of the one or more request handlers to process the request, wherein the one or more request handler comprise an Internal Routing Message Protocol (Irmp) request handler;

passing the connection from the request manager associated with the connection to a request handler of the one or more of the request handlers, wherein the request handler is configured to read data off the connection;

unmarshalling the marshaled request with the request handler to provide an unmarshalled request;

passing arguments related to the unmarshalled request to a server object via an adapter object, wherein the server object includes at least one operation, and wherein the adapter object is configured to call the server object by mapping a name of said at least one operation to an associated operation;

receiving a response related to the arguments from the server object via the adapter object;

marshalling the response to provide a marshaled response; and

passing the marshaled response to the entity effective to cause the marshaled response to be unmarshalled and passed from the entity to a proxy object and from the proxy object to a client application that requested the unmarshalled marshaled response.

12. The method of claim 11, wherein unmarshalling the marshaled request includes unmarshalling a marshaled request that includes at least one of the arguments or an identifier associated with the adapter object and an Object Request Broker (ORB) server.

13. The method of claim 12, further comprising passing the marshaled request and the unmarshalled marshaled response according to a specific protocol.

14. The method of claim 11, wherein unmarshalling the marshaled request includes unmarshalling a marshaled request that includes the arguments and an identifier associated with the adapter object and an Object Request Broker (ORB) server and further comprising:

using, with the ORB server, the identifier to look up the adapter object; and

using an acquired connection with the entity to pass the marshaled request and the unmarshalled marshaled response.

15. The method of claim 11, further comprising binding the adapter object within a naming service, the binding associating the adapter object to a Universal Resource Locator (URL) within the naming service.

16. A non-transitory computer-readable medium having stored thereon, computer-executable instructions that, in response to execution by a device, cause the device to:

receive an incoming call, with a request manager, from an entity, wherein the incoming call includes a marshaled request related to arguments associated with a different call from a client business object to a proxy object and wherein the request manager is associated with a connection;

query one or more request handlers as to the respective abilities of the one or more request handlers to process the incoming call, wherein the one or more request handler comprise an Internal Routing Message Protocol (Irmp) request handler;

pass the connection from the request manager associated with the connection to a request handler of the one the or more request handlers, wherein the said one request handler is configured to read data off the connection;

process the call with the request handler;

call an adapter via the request handler, wherein calling the adapter includes unmarshalling the marshaled request;

call a server business object via the adapter effective to pass the arguments associated with the different call to the server business object, wherein the server business object includes at least one operation, and wherein the adapter is configured to call the server business object by mapping a name of said at least one operation to an associated operation;

receive with the request handler, a response from the server business object via the adapter; and

call with the request handler, the entity effective to marshal the response and pass the marshaled response to the entity, effective to cause a reply including an unmarshalled marshaled response to be returned to the proxy object, and effective to cause a reply including the unmarshalled marshaled response to be returned to the client business object.

17. The non-transitory computer-readable medium of claim 16, wherein the marshaled request includes at least one of the arguments or an identifier associated with the adapter and an Object Request Broker (ORB) server, and the marshaled request and the unmarshalled marshaled response are passed according to a specific protocol.

18. The non-transitory computer-readable medium of claim 16, wherein the marshaled request includes the arguments and an identifier associated with the adapter and an Object Request Broker (ORB) server and wherein the device is further caused to:

use, with the ORB server, the identifier to look up the adapter; and

use an acquired connection with the entity to pass the marshaled request and the unmarshalled marshaled response.