System and method for a pluggable protocol handler

• US 20070067469A1
• Filed: 07/19/2005
• Published: 03/22/2007
• Est. Priority Date: 07/19/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Galchev, Galin, Luik, Oliver
• Granted Patent: US 7,966,412 B2
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Abstract

Embodiments of the invention are generally directed to a system and method for pluggable protocol handlers to route message traffic between communication partners. In an embodiment, a protocol independent connection manager receives a message from a communication partner over a network connection. The connection manager calls a dynamically loadable protocol handler to process and route the received message to a subsequent communication partner. In one embodiment, the network connection is a multiplexed network connection.

Claims

1. A system comprising:

a protocol independent connection manager to receive a message from a communication partner on a network connection endpoint; and

a dynamically loadable communication protocol handler coupled with the connection manager, the dynamically loadable communication protocol handler to forward the message to another communication partner.

2. The system of claim 1, wherein the network connection is a multiplexed network connection.

3. The system of claim 2, wherein the dynamically loadable communication protocol handler implements, at least in part, a standards-based communication protocol.

4. The system of claim 3, wherein the standards-based communication protocol is the Internet Inter-Object Request Broker Protocol.

5. The system of claim 2, wherein the dynamically loadable communication protocol handler implements, at least in part, a proprietary communication protocol.

6. The system of claim 5, wherein the proprietary communication protocol is the P4 protocol.

7. The system of claim 2, wherein the communication partner is one of:

an internal communication partner; and

an external communication partner.

8. The system of claim 7, wherein the internal communication partner is a worker node.

9. The system of claim 8, wherein the multiplexed network connection is implemented with a connection oriented shared memory.

10. A method comprising:

receiving at a dynamically loadable communication protocol handler an indication that a network connection endpoint is available for an input/output function; and

performing the input/output function of the dynamically loadable communication protocol handler responsive, at least in part, to receiving the indication.

11. The method of claim 10, further comprising:

registering one or more input/output functions of the dynamically loadable communication protocol handler with a connection manager, the one or more input/output functions to allow the connection manager to call the dynamically loadable communication protocol handler.

12. The method of claim 10, wherein receiving at a dynamically loadable communication protocol handler an indication that the network connection endpoint is available for an input/output function comprises:

receiving at the dynamically loadable communication protocol handler an indication that a multiplexed network connection endpoint is available for an input/output function.

13. The method of claim 10, wherein receiving at a dynamically loadable communication protocol handler an indication that the network connection endpoint is available for an input/output function comprises:

receiving a handle from a select thread indicating that the network connection endpoint is available for an input/output function.

14. The method of claim 13, wherein receiving a handle includes receiving a handle for a read function and further comprising:

reading at least part of a message from the network connection endpoint.

15. The method of claim 14, wherein reading at least part of the message from the network connection comprises:

reading at least a part of a message header associated with the message; and

determining a destination for the message based, at least in part, on the message header.

16. The method of claim 15, wherein the message header is based, at least in part, on one of:

a standards-based communication protocol; and

a proprietary communication protocol.

17. The method of claim 16, wherein the standards-based communication protocol is the Internet Inter-Object Request Broker Protocol.

18. An article of manufacturer comprising an electronically accessible medium providing instructions that, when executed by an apparatus, cause the apparatus to:

receive at a dynamically loadable communication protocol handler an indication that a network connection endpoint is available for an input/output function; and

perform the input/output function of the dynamically loadable communication protocol handler responsive, at least in part, to receiving the indication.

19. The article of manufacture of claim 18, wherein the electronically accessible medium provides further instructions that, when executed by the apparatus, cause the apparatus to:

register one or more input/output functions of the dynamically loadable communication protocol handler with a connection manager, the one or more input/output functions to allow the connection manager to call the dynamically loadable communication protocol handler.

20. The article of manufacture of claim 18, wherein the instructions that, when executed by the apparatus, cause the apparatus to receive at the dynamically loadable communication protocol handler the indication that the network connection endpoint is available for an input/output function cause the apparatus to:

receive a handle from a select thread indicating that the network connection endpoint is available for an input/output function.