US7010609B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
System and method for adding transport protocols in distributed middleware applications
Assignee: Borland Software Corp
•
Filing: 2000-12-21
•
Granted: 2006-03-07
•
Expires: 2020-12-21
Abstract
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.
Inventors
- 👤 Kenneth R. Black
- 👤 Robert M. Jensen
- 👤 Jorge E. Rodriguez
- 👤 Jonathan J. Currey
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-30 02:19
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/46; G06F9/54; G06F9/546; G06F2209/00; G06F2209/54; G06F2209/547; H; H04; H04L; H04L69/00; H04L69/18; H04L69/30; H04L69/32; H04L69/322; H04L69/326
Claims Analysis
Total Claims: 11
Claim 1
Independent Claim
228 words
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.
Claim 2
Independent Claim
228 words
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.
Claim 3
Dependent Claim
31 words
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.
Claim 4
Dependent Claim
21 words
The method of claim 1 , wherein said connection bridge further communicates with multiple protocol instances and different types of protocols.
Claim 5
Dependent Claim
21 words
The method of claim 1 , wherein said connection bridge further communicates with existing internally supported transport protocols of the middleware.
Claim 6
Dependent Claim
15 words
The method claim 1 , further including performing said steps in an object-oriented programming language.
Claim 7
Dependent Claim
19 words
The method of claim 1 , including implementing said connection bridge by utilizing a synchronization primitive and FIFO queue.
Claim 8
Dependent Claim
22 words
The method of claim 1 , wherein the communication between the first application software and the second application software comprises executable code.
Claim 9
Dependent Claim
52 words
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.
Claim 10
Dependent Claim
24 words
The method of claim 8 , wherein the first application software is a client software and the second application software is a server software.
Claim 11
Dependent Claim
14 words
The method of claim 1 , wherein the second computer is an embedded computer.
References Cited (Backward Citations)
US6125388A
Cited
US6611862B2
Cited
US5960204A
Cited
US6026404A
Cited
US5903728A
Cited
US5974566A
Cited
US6209018B1
Cited
US6412073B1
Cited
US6721799B1
Cited
US6622017B1
Cited
US20020107977A1
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2009-03-06 | 2009-09-05 | 2010-03-07 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2013-03-06 | 2013-09-05 | 2014-03-07 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2017-03-06 | 2017-09-05 | 2018-03-07 | $7700.00 | Window Closed / Lapsed |