Skip to content

Commit

Permalink
Added docu on FORWARD_TO_COORD
Browse files Browse the repository at this point in the history
  • Loading branch information
belaban committed Sep 12, 2012
1 parent 58117bf commit c484710
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions doc/manual/en/modules/advanced.xml
Expand Up @@ -1926,13 +1926,20 @@ On view change V:
<programlisting language="XML">
&lt;relay.RELAY2 site="LON" config="/home/bela/relay2.xml"
relay_multicasts="true" /&gt;
&lt;FORWARD_TO_COORD /&gt;
</programlisting>

<para>
The above configuration has a site name which will be used to route messages between sites. To do that, addresses
contain the site-ID, so we always know which site the address is from. E.g. an address A1:LON in the SFO site
is not local, but will be routed to the remote site SFO.
</para>
<para>
The FORWARD_TO_COORD protocol is optional, but since it guarantees reliable message forwarding to the local
site master, it is recommended. It makes sure that - if a local coordinator (site master) crashes or leaves
while a message is being forwarded to it - the message will be forwarded to the next coordinator once
elected.
</para>
<para>
The relay_multicasts property determines whether or not multicast messages (with dest = null) are relayed to
the other sites, or not. When we have a site LON, connected to sites SFO and NYC, if a multicast message is
Expand Down

0 comments on commit c484710

Please sign in to comment.