System and method for adding transport protocols in distributed middleware applications

• US 7,010,609 B1
• Filed: 12/21/2000
• Issued: 03/07/2006
• Est. Priority Date: 12/21/2000
• Status: Expired due to Fees

• Current Assignee: Borland Software Corporation (Open Text Corporation)
• Original Assignee: Borland Software Corporation (Open Text Corporation)
• Inventors: Jensen, Robert M., Black, Kenneth R., Currey, Jonathan J., Rodriguez, Jorge E.
• Primary Examiner(s): Burgess, Glenton B.
• Assistant Examiner(s): BARQADLE, YASIN M
• Application Number:
  US09/747,353
• Time in Patent Office: 1,902 Days
• Field of Search: 719311-332, 719/310, 709220-223, 709/227, 709229-230, 709/238, 709/250, 709201-203, 717136-137, 717/17
• US Class Current: 709/230
• CPC Class Codes: G06F 2209/547 Messaging middleware
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence

Abstract

A connection bridge mechanism for adding arbitrary protocols into a middleware-based application without accessing the source code for the middleware or producing a new version of the middleware source code. Using a connection bridge allows the plugged in protocol to be utilized by the middleware without requiring that the same O/S primitives which are utilized internally by the middleware be supported by the plugged in protocol. The plugged in protocol can be utilized in addition to the internally supported middleware protocols or it can replace the existing middleware protocols. The connection bridge provides the communication between the protocols and the middleware package. The connection bridge queues the requests from the protocols and notifies the middleware when there are requests pending for action by the middleware.

Claims

1. A method for allowing arbitrary protocols to be added or plugged into a distributed application utilizing middleware for communication without accessing the source code for the middleware or producing a new version of the middleware source code, comprising the steps of:

providing a first computer executing middleware, one or more transport protocols and first application software, the first application software being part of the distributed application;

providing a second computer executing second application software, the second application software being part of the distributed application;

providing a connection bridge for communicating between the one or more transport protocols and the middleware of the first computer;

as a result of communication between the first application software and the second application software, generating an action requests by at least one transport protocol of the one or more transport protocols, the action request including a protocol connection identifier;

sending the action request to the connection bridge;

said connection bridge notifying said middleware that an action request is ready to have an action performed;

said connection bridge transferring said protocol connection identifier to said middleware; and

adding to the middleware of the first computer an additional transport protocol in support of communication between the first and second application software using the protocol connection identifier and without accessing the source code for the middleware or producing the new version of the middleware source code.

2. The method of claim 1, wherein said at least one transport protocol is such that the middleware is not configured to directly communicate with said at least one transport protocol.

3. The method of claim 1, wherein said connection bridge further communicates with multiple protocol instances and different types of protocols.

4. The method of claim 1, wherein said connection bridge further communicates with existing internally supported transport protocols of the middleware.

5. The method claim 1, further including performing said steps in an object-oriented programming language.

6. The method of claim 1, including implementing said connection bridge by utilizing a synchronization primitive and FIFO queue.

7. The method of claim 1, wherein the communication between the first application software and the second application software comprises executable code.

8. The method of claim 7, wherein the communication between the first application software and the second application software further comprises an invocation of an object residing at the second computer by the first application software and the sending of the object to the first application software by the second application software.

9. The method of claim 8, wherein the first application software is a client software and the second application software is a server software.

10. The method of claim 1, wherein the second computer is an embedded computer.