TIBCO Rendezvous: Difference between revisions

TIBCO Rendezvous
Developer(s)	TIBCO Software
Stable release	8
Operating system	Cross-platform
Type	Message-oriented middleware
License	Proprietary
Website	www.tibco.com

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Inline

Latest revision as of 15:49, 20 April 2023

TIBCO Rendezvous is a software product that provides a message bus for enterprise application integration (EAI).

Details

TIBCO provides messaging APIs in C, C++, Java, Visual Basic, Perl and .NET to provide messaging between two or more services.

The basic message passing is conceptually simple:

A message has a single subject composed of elements separated by periods. A message is sent to a single Rendezvous Daemon (though it may end up being broadcast onto Daemons).
A listener announces its subjects of interest to a Daemon (with a basic wildcard facility) and messages with matching subjects are delivered to it if the two daemons are 'connected' to each other (or indeed the same daemon).

Considerable "Enterprise" functionality is layered onto this if desired with Fault Tolerance/Reliable or Certified options possible, all implemented through the underlying basic messages.

The messages themselves can be viewed as typed name-value fields and/or number-value fields (the two identification mechanisms within a message can mix and match with certain restrictions). A message can itself contain sub-messages which themselves may contain sub-messages, and so on.

The quality of the respective API implementations varies considerably. The C++ library is simply a wrapper providing an OO view over the C implementation. Likewise the Java and .NET implementations wrap the C++ implementation. This has led to memory management issues with the .NET implementation (though not with the COM Interop version which is considerably more cumbersome).

External links

TIBCO Rendezvous (Official site)
TIBCO Rendezvous - Message Board

References

This programming-tool-related article is a stub. You can help Wikipedia by expanding it.

@@ Line 1: / Line 1: @@
+{{Short description|Software for messaging between programs}}
-'''TIBCO Rendezvous''' is a software product that provides a message bus for [[enterprise application integration]] (EAI).
+{{Multiple issues|
+{{Primary sources|date=March 2007}}
+{{notability|Products|date=September 2015}}
+}}
+{{Infobox software
+| name = TIBCO Rendezvous
+| logo =
+| screenshot =
+| caption = TIBCO Rendezvous
+| developer = [[TIBCO Software]]
+| latest_release_version = 8
+| latest_release_date =
+| programming_language =
+| operating_system = [[Cross-platform]]
+| genre = [[Message-oriented middleware]]
+| license = Proprietary
+| website = [http://www.tibco.com/products/automation/enterprise-messaging/rendezvous www.tibco.com]
+}}
+'''TIBCO Rendezvous''' is a [[software]] product that provides a message bus for [[enterprise application integration]] (EAI).
-[[TIBCO]] provides messaging [[application programming interface|API]]s in [[C (programming language)|C]], [[C++]], [[Java (programming language)|Java]], [[Visual BASIC ]] and [[Microsoft .NET|.NET]] to receive data feeds on [[Microsoft Excel|Excel]] spreadsheets and other applications of choice.
+==Details==
+[[TIBCO]] provides messaging [[application programming interface|API]]s in [[C (programming language)|C]], [[C++]], [[Java (programming language)|Java]], [[Visual Basic]], [[Perl]] and [[Microsoft .NET|.NET]] to provide messaging between two or more services.
 The basic message passing is conceptually simple:
@@ Line 7: / Line 28: @@
 * A listener announces its subjects of interest to a Daemon (with a basic wildcard facility) and messages with matching subjects are delivered to it if the two daemons are 'connected' to each other (or indeed the same daemon).
-Considerable "Enterprise" functionality is layered onto this if desired with Fault Tolerance / Reliable or Certified options possible all implemented through the underlying basic messages.
+Considerable "Enterprise" functionality is layered onto this if desired with Fault Tolerance/Reliable or Certified options possible, all implemented through the underlying basic messages.
 The messages themselves can be viewed as typed name-value fields and/or number-value fields (the two identification mechanisms within a message can mix and match with certain restrictions). A message can itself contain sub-messages which themselves may contain sub-messages, and so on.
-The quality of the respective API's implementation varies considerably. The C++ library is simply a wrapper providing an OO view over the C implementation. Likewise the Java and .NET implementations wrap the C++ implementation. This has lead to memory management issues with the .NET implementation (though not with the COM Interop version which is considerably more cumbersome).
+The quality of the respective API implementations varies considerably. The C++ library is simply a wrapper providing an OO view over the C implementation. Likewise the Java and .NET implementations wrap the C++ implementation. This has led to memory management issues with the .NET implementation (though not with the COM Interop version which is considerably more cumbersome).
 ==External links==
-*[http://www.tibco.com/software/messaging/rendezvous/default.jsp TIBCO Rendezvous] (Official site)
+*[http://www.tibco.com/products/automation/enterprise-messaging/rendezvous TIBCO Rendezvous] (Official site)
+*[https://web.archive.org/web/20120315230614/http://www.tibco.talk2experts.com/forums/viewforum.php?f=21%2F TIBCO Rendezvous - Message Board ]
+==References==
-{{primarysources}}
+{{reflist}}
 [[Category:Message-oriented middleware]]
+{{programming-software-stub}}