您好，我是 Tibco RV 的新手。读完 Tibco Rendezvous Concept 后，我仍然对传输参数感到困惑：服务、网络、守护进程。
因此从概念上讲，每台机器上只运行一个守护进程。因此，当使用 tibrvsend 时：
tibrvsend -service 2323 -network "someIPAddress" -daemon "myDaemon" MESSAGE
这是否意味着我正在使用本地主机上的端口 2323，通过守护进程 myDaemon （可能位于远程）向网络 comeIPAddress 发送消息？
使用 tibrvlisten 时：
tibrvListen -service 2323 -network "someIPAddress" -daemon "myDaemon"
这是否意味着我正在使用本地主机上的任何可用端口、任何可用守护进程来侦听来自发布到 someIPAddress 的 myDaemon 端口 2323 的消息 另一个问题是，《Tibco RV Concept》一书中提到同一个服务不能绑定到两个网络
，它是否只适用于生产者机器（因为我们没有为侦听器机器指定端口）？如果我们这样做：
tibrvsend -service 2323 -network "net1" MESSAGE
并且
tibrvsend -service 2323 -network "net2" MESSAGE
同时（如果我们连续这样做应该没问题，对吧？）
但是对于听众来说：
tibrvlisten -service 2323 -network "net1"
并且
tibrvlisten -service 2323 -network "net2"
应该完全没问题（否则这意味着生产者需要知道彼此的端口号以避免冲突）
如果我完全搞乱了这些概念，你能用例子解释一下吗？
Hi I am new to Tibco RV. After reading the Tibco Rendezvous Concept, I am still confused about the transport parameters: service, network, daemon.
So conceptually there is only one daemon running on each machine. So when using tibrvsend:
tibrvsend -service 2323 -network "someIPAddress" -daemon "myDaemon" MESSAGE
Does it mean I am sending message using port 2323 on my localhost, through daemon myDaemon (which could be on remote), to network comeIPAddress?
When using tibrvlisten:
tibrvListen -service 2323 -network "someIPAddress" -daemon "myDaemon"
Does it mean I am listening using any available port, any available daemon on my localhost, to listen the messages from port 2323 of myDaemon" that published to someIPAddress network?
Another question is, the book "Tibco RV Concept" mentioned that the same service cannot be bind to two networks. Does it only apply to producer machines (since we don't specify port for listener machine)? So an error will occur if we do:
tibrvsend -service 2323 -network "net1" MESSAGE
and
tibrvsend -service 2323 -network "net2" MESSAGE
at the same time (it should be OK if we do it consecutively, right?)
but for listeners:
tibrvlisten -service 2323 -network "net1"
and
tibrvlisten -service 2323 -network "net2"
should be perfectly fine? (otherwise it means producers need to know each others' port number in order to avoid conflict)
If I have totally messed up with the concepts, can you please explain with examples?
发布评论
评论（2）
您可以在一台计算机上运行多个守护进程，但这不是必需的。您可以通过改变服务和网络参数来访问单个守护程序上的多个逻辑总线。
守护进程是在您的计算机上运行的实际进程，用于处理 Rendezvous 消息传递。您的客户端将使用 daemon 参数连接到此守护程序。例如，默认值
tcp:7500将访问本地计算机上端口 7500 上的守护程序，而值tcp:server.domain.com:8000将访问守护程序在端口 8000 上的远程计算机 (server.domain.com) 上。示例：如果执行
tibrvlisten -daemon tcp:8000，您会注意到有一个新进程在机器上启动（Windows 上的 rvd.exe，Unix 上的 rvd）侦听端口 8000。服务和网络参数依次是多播参数（请参阅 http://en.wikipedia.org/wiki/Multicast）。为了简化，您可以将这些视为相当抽象的值，具有两个重要方面：
关于 Rendezvous 需要记住的另一件事是，同一子网上的所有计算机都会接收多播消息。如果您需要将消息发送到其他子网，则应考虑使用 Rendezvous Routing Daemons (RVRD)。
You can have several daemons running on a single machine, but it isn't necessary. You can access several logical buses on a single daemon by varying the service and network parameters.
The daemon is the actual process running on your machine to handle Rendezvous messaging. Your clients will connect to this daemon using the daemon parameter. E.g. the default value
tcp:7500will access a daemon on the local machine on port 7500, whereas a value oftcp:server.domain.com:8000will access a daemon on a remote machine (server.domain.com) on port 8000.Example: If you execute
tibrvlisten -daemon tcp:8000you will note that a new process is started on the machine (rvd.exe on Windows, rvd on Unix) listening to port 8000.The service and network parameters in turn are multicast parameters (see http://en.wikipedia.org/wiki/Multicast). To simplify you can view these as rather abstract values, with two important facets:
Another thing to keep in mind regarding Rendezvous is that multicast messages are received by all machines on the same subnet. If you need to send messages to other subnets, you should consider using Rendezvous Routing Daemons (RVRD).
服务：它是一个udp端口，基于udp协议的TRDP（Tibco可靠数据报协议）。
守护进程：RVD 进程使用的 tcp 端口。应用程序通过 TCP 端口与 RVD 进程进行通信。 RVD使用TCP端口接收消息并通过udp端口发送出去
网络：E类IP地址，它是组播IP地址
Service : it's a udp port, TRDP (Tibco Reliable Data-gram Protocol ) based on udp protocol .
Daemon : tcp ports used by RVD process. Application programs communicate with RVD process via TCP ports. RVD use TCP port to receive messages and send it out by udp port
network : E class IP address, it's multicast IP address