TIBRV: Remote vs Local RVD
Posted
by jsw
on Stack Overflow
See other posts from Stack Overflow
or by jsw
Published on 2010-04-07T22:52:34Z
Indexed on
2010/05/28
19:32 UTC
Read the original article
Hit count: 399
When connected to a local RVD a sending application is shielded from network interruptions and the send message methods will only block for the time it takes for the message to reach the local RVD process.
With remote RVD the sending application is no longer shielded from network interruptions and the send message methods will block for the time it takes to hop across the network to reach the remote RVD process.
Is my understanding correct? The documentation is vague regarding remote daemons.
I'm mostly concerned with how reliable and performant the send message will be from the perspective of a sending application. Introducing unnecessary blocking on the client side due to sending a message (especially a network hop) is a big no-no in this application. The speed at which the messages reach the consumer is not of the utmost importance. With this in mind is a remote RVD out of the question?
© Stack Overflow or respective owner