edgepeerrdvservice.html

jxta的api库

               throws java.io.IOException</PRE>
<DL>
<DD>Propagates a message onto as many peers on the local network
 as possible. Typically the message will go to all the peers to
 which at least one endpoint transport can address without using
 the router.

 This method sends the message to all peers, rendezvous peers and
 edge peer. This method of propation is very expensive and should
 not be frequentely used. When rendezvous peers are used in order to
 cache index of data, it is more efficient to use the walk() method.

 Only a single HOP at a time is performed. Messages are always
 delivered to the destination handler on arrival. This handler
 is responsible for repropagating further, if deemed appropropriate.

 Loop and TTL control are performed automatically.

 Messages can be propagated via this method for the first time or
 can be re-propagated by re-using a message that came in via propagation.
 In the later case, the TTL and loop detection parameters CANNOT be
 re-initialized. If one wants to "re-propagate" a message with a new TTL
 and blank gateways list one must generate a completely new message.
 This limits the risk of accidental propagation storms, although they
 can always be engineered deliberately.

 Note: The original msg is not modified and may be reused upon return.
<P>
<DD><DL>
<DT><B>Specified by:</B><DD><CODE><A HREF="../../../../../net/jxta/impl/rendezvous/RendezVousServiceProvider.html#propagate(net.jxta.endpoint.Message, java.lang.String, java.lang.String, int)">propagate</A></CODE> in class <CODE><A HREF="../../../../../net/jxta/impl/rendezvous/RendezVousServiceProvider.html" title="class in net.jxta.impl.rendezvous">RendezVousServiceProvider</A></CODE></DL>
</DD>
<DD><DL>
<DT><B>Parameters:</B><DD><CODE>msg</CODE> - is the message to propagate.<DD><CODE>serviceName</CODE> - is the name of the service<DD><CODE>serviceParam</CODE> - is the parameter of the service
<DT><B>Throws:</B>
<DD><CODE>java.io.IOException</CODE></DL>
</DD>
</DL>
<HR>

<A NAME="propagate(java.util.Enumeration, net.jxta.endpoint.Message, java.lang.String, java.lang.String, int)"><!-- --></A><H3>
propagate</H3>
<PRE>
public void <B>propagate</B>(java.util.Enumeration&nbsp;destPeerIDs,
                      <A HREF="../../../../../net/jxta/endpoint/Message.html" title="class in net.jxta.endpoint">Message</A>&nbsp;msg,
                      java.lang.String&nbsp;serviceName,
                      java.lang.String&nbsp;serviceParam,
                      int&nbsp;defaultTTL)
               throws java.io.IOException</PRE>
<DL>
<DD>Propagates a message onto as many peers on the local network
 as possible. Typically the message will go to all the peers to
 which at least one endpoint transport can address without using
 the router.

 This method sends the message to all peers, rendezvous peers and
 edge peer. This method of propation is very expensive and should
 not be frequentely used. When rendezvous peers are used in order to
 cache index of data, it is more efficient to use the walk() method.

 Only a single HOP at a time is performed. Messages are always
 delivered to the destination handler on arrival. This handler
 is responsible for repropagating further, if deemed appropropriate.

 Loop and TTL control are performed automatically.

 Messages can be propagated via this method for the first time or
 can be re-propagated by re-using a message that came in via propagation.
 In the later case, the TTL and loop detection parameters CANNOT be
 re-initialized. If one wants to "re-propagate" a message with a new TTL
 and blank gateways list one must generate a completely new message.
 This limits the risk of accidental propagation storms, although they
 can always be engineered deliberately.

 Note: The original msg is not modified and may be reused upon return.
<P>
<DD><DL>
<DT><B>Specified by:</B><DD><CODE><A HREF="../../../../../net/jxta/impl/rendezvous/RendezVousServiceProvider.html#propagate(java.util.Enumeration, net.jxta.endpoint.Message, java.lang.String, java.lang.String, int)">propagate</A></CODE> in class <CODE><A HREF="../../../../../net/jxta/impl/rendezvous/RendezVousServiceProvider.html" title="class in net.jxta.impl.rendezvous">RendezVousServiceProvider</A></CODE></DL>
</DD>
<DD><DL>
<DT><B>Parameters:</B><DD><CODE>msg</CODE> - is the message to propagate.<DD><CODE>serviceName</CODE> - is the name of the service<DD><CODE>serviceParam</CODE> - is the parameter of the service
<DT><B>Throws:</B>
<DD><CODE>java.io.IOException</CODE></DL>
</DD>
</DL>
<HR>

<A NAME="propagateToNeighbors(net.jxta.endpoint.Message, java.lang.String, java.lang.String, int, java.lang.String)"><!-- --></A><H3>
propagateToNeighbors</H3>
<PRE>
public void <B>propagateToNeighbors</B>(<A HREF="../../../../../net/jxta/endpoint/Message.html" title="class in net.jxta.endpoint">Message</A>&nbsp;msg,
                                 java.lang.String&nbsp;serviceName,
                                 java.lang.String&nbsp;serviceParam,
                                 int&nbsp;defaultTTL,
                                 java.lang.String&nbsp;prunePeer)
                          throws java.io.IOException</PRE>
<DL>
<DD>Propagates a message onto as many peers on the local network
 as possible. Typically the message will go to all the peers to
 which at least one endpoint transport can address without using
 the router.

 Only a single HOP at a time is performed. Messages are always
 delivered to the destination handler on arrival. This handler
 is responsible for repropagating further, if deemed appropropriate.

 Loop and TTL control are performed automatically.

 Messages can be propagated via this method for the first time or
 can be re-propagated by re-using a message that came in via propagation.
 In the later case, the TTL and loop detection parameters CANNOT be
 re-initialized. If one wants to "re-propagate" a message with a new TTL
 and blank gateways list one must generate a completely new message.
 This limits the risk of accidental propagation storms, although they
 can always be engineered deliberately.

 Note: The original msg is not modified and may be reused upon return.
<P>
<DD><DL>
<DT><B>Specified by:</B><DD><CODE><A HREF="../../../../../net/jxta/impl/rendezvous/RendezVousServiceProvider.html#propagateToNeighbors(net.jxta.endpoint.Message, java.lang.String, java.lang.String, int, java.lang.String)">propagateToNeighbors</A></CODE> in class <CODE><A HREF="../../../../../net/jxta/impl/rendezvous/RendezVousServiceProvider.html" title="class in net.jxta.impl.rendezvous">RendezVousServiceProvider</A></CODE></DL>
</DD>
<DD><DL>
<DT><B>Parameters:</B><DD><CODE>msg</CODE> - is the message to propagate.<DD><CODE>serviceName</CODE> - is the name of the service<DD><CODE>serviceParam</CODE> - is the parameter of the service<DD><CODE>prunePeer</CODE> - is a peer to prune in the propagation.
<DT><B>Throws:</B>
<DD><CODE>java.io.IOException</CODE></DL>
</DD>
</DL>
<HR>

<A NAME="propagateInGroup(net.jxta.endpoint.Message, java.lang.String, java.lang.String, int, java.lang.String)"><!-- --></A><H3>
propagateInGroup</H3>
<PRE>
public void <B>propagateInGroup</B>(<A HREF="../../../../../net/jxta/endpoint/Message.html" title="class in net.jxta.endpoint">Message</A>&nbsp;msg,
                             java.lang.String&nbsp;serviceName,
                             java.lang.String&nbsp;serviceParam,
                             int&nbsp;defaultTTL,
                             java.lang.String&nbsp;prunePeer)
                      throws java.io.IOException</PRE>
<DL>
<DD>Propagates a message onto as many peers in the group as possible.

 Only a single HOP at a time is performed. Messages are always
 delivered to the destination handler on arrival. This handler
 is responsible for repropagating further, if deemed appropropriate.

 Loop and TTL control are performed automatically.

 Messages can be propagated via this method for the first time or
 can be re-propagated by re-using a message that came in via propagation.
 In the later case, the TTL and loop detection parameters CANNOT be
 re-initialized. If one wants to "re-propagate" a message with a new TTL
 and blank gateways list one must generate a completely new message.
 This limits the risk of accidental propagation storms, although they
 can always be engineered deliberately.

 Note: The original msg is not modified and may be reused upon return.
<P>
<DD><DL>
<DT><B>Specified by:</B><DD><CODE><A HREF="../../../../../net/jxta/impl/rendezvous/RendezVousServiceProvider.html#propagateInGroup(net.jxta.endpoint.Message, java.lang.String, java.lang.String, int, java.lang.String)">propagateInGroup</A></CODE> in class <CODE><A HREF="../../../../../net/jxta/impl/rendezvous/RendezVousServiceProvider.html" title="class in net.jxta.impl.rendezvous">RendezVousServiceProvider</A></CODE></DL>
</DD>
<DD><DL>
<DT><B>Parameters:</B><DD><CODE>msg</CODE> - is the message to propagate.<DD><CODE>serviceName</CODE> - is the name of the service<DD><CODE>serviceParam</CODE> - is the parameter of the service<DD><CODE>prunePeer</CODE> - is a peer to prune in the propagation.
<DT><B>Throws:</B>
<DD><CODE>java.io.IOException</CODE></DL>
</DD>
</DL>
<HR>

<A NAME="rePropagateInGroup(net.jxta.endpoint.Message)"><!-- --></A><H3>
rePropagateInGroup</H3>
<PRE>
protected void <B>rePropagateInGroup</B>(<A HREF="../../../../../net/jxta/endpoint/Message.html" title="class in net.jxta.endpoint">Message</A>&nbsp;msg)</PRE>
<DL>
<DD><DL>
</DL>
</DD>
</DL>
<HR>

<A NAME="gc()"><!-- --></A><H3>
gc</H3>
<PRE>
public void <B>gc</B>()</PRE>
<DL>
<DD>Clean up any dead references.
<P>
<DD><DL>
<DT><B>Specified by:</B><DD><CODE><A HREF="../../../../../net/jxta/impl/rendezvous/RendezVousServiceProvider.html#gc()">gc</A></CODE> in class <CODE><A HREF="../../../../../net/jxta/impl/rendezvous/RendezVousServiceProvider.html" title="class in net.jxta.impl.rendezvous">RendezVousServiceProvider</A></CODE></DL>
</DD>
<DD><DL>
</DL>
</DD>
</DL>
<HR>

<A NAME="isMessageValid(net.jxta.impl.rendezvous.RendezVousPropagateMessage)"><!-- --></A><H3>
isMessageValid</H3>
<PRE>
public boolean <B>isMessageValid</B>(<A HREF="../../../../../net/jxta/impl/rendezvous/RendezVousPropagateMessage.html" title="class in net.jxta.impl.rendezvous">RendezVousPropagateMessage</A>&nbsp;propHdr)</PRE>
<DL>
<DD>{@inheritDoc}
<P>
<DD><DL>
<DT><B>Specified by:</B><DD><CODE><A HREF="../../../../../net/jxta/impl/rendezvous/RendezVousServiceProvider.html#isMessageValid(net.jxta.impl.rendezvous.RendezVousPropagateMessage)">isMessageValid</A></CODE> in class <CODE><A HREF="../../../../../net/jxta/impl/rendezvous/RendezVousServiceProvider.html" title="class in net.jxta.impl.rendezvous">RendezVousServiceProvider</A></CODE></DL>
</DD>
<DD><DL>
</DL>
</DD>
</DL>
<HR>

<A NAME="walk(net.jxta.endpoint.Message, java.lang.String, java.lang.String, int)"><!-- --></A><H3>
walk</H3>
<PRE>
public void <B>walk</B>(<A HREF="../../../../../net/jxta/endpoint/Message.html" title="class in net.jxta.endpoint">Message</A>&nbsp;msg,
                 java.lang.String&nbsp;serviceName,
                 java.lang.String&nbsp;serviceParam,
                 int&nbsp;defaultTTL)
          throws java.io.IOException</PRE>
<DL>
<DD><B>Description copied from class: <CODE><A HREF="../../../../../net/jxta/impl/rendezvous/RendezVousServiceProvider.html" title="class in net.jxta.impl.rendezvous">RendezVousServiceProvider</A></CODE></B></DD>
<DD>Walk a message through the rendezvous peers of the network: only
 rendezvous peers will receive the message.

 Only a single HOP at a time is performed. Messages are always
 delivered to the destination handler on arrival. This handler
 is responsible for repropagating further, if deemed appropropriate.

 Loop and TTL control are performed automatically.

 Messages can be propagated via this method for the first time or
 can be re-propagated by re-using a message that came in via propagation.
 In the later case, the TTL and loop detection parameters CANNOT be
 re-initialized. If one wants to "re-propagate" a message with a new TTL
 and blank gateways list one must generate