rendezvousserviceprovider.html

jxta的api库

<DD>Stop the RendezVous function on the local Peer. All connected Peer are
 disconnected.
<P>
<DD><DL>
</DL>
</DD>
<DD><DL>
</DL>
</DD>
</DL>
<HR>

<A NAME="getConnectedPeers()"><!-- --></A><H3>
getConnectedPeers</H3>
<PRE>
public abstract java.util.Enumeration <B>getConnectedPeers</B>()</PRE>
<DL>
<DD>Returns an Enumeration of PeerID of the peers that are currentely
 connected.
<P>
<DD><DL>
</DL>
</DD>
<DD><DL>

<DT><B>Returns:</B><DD>Enumeration enumeration of peers connected to that rendezvous</DL>
</DD>
</DL>
<HR>

<A NAME="getConnectedPeerIDs()"><!-- --></A><H3>
getConnectedPeerIDs</H3>
<PRE>
public abstract java.util.Vector <B>getConnectedPeerIDs</B>()</PRE>
<DL>
<DD>Returns a Vector of PeerID of the peers that are currentely
 connected.
<P>
<DD><DL>
</DL>
</DD>
<DD><DL>

<DT><B>Returns:</B><DD>Vector vector of peers connected to that rendezvous</DL>
</DD>
</DL>
<HR>

<A NAME="sendRendezVousAdv(net.jxta.protocol.PeerAdvertisement, net.jxta.protocol.PeerAdvertisement)"><!-- --></A><H3>
sendRendezVousAdv</H3>
<PRE>
public abstract void <B>sendRendezVousAdv</B>(<A HREF="../../../../net/jxta/protocol/PeerAdvertisement.html" title="class in net.jxta.protocol">PeerAdvertisement</A>&nbsp;destPeer,
                                       <A HREF="../../../../net/jxta/protocol/PeerAdvertisement.html" title="class in net.jxta.protocol">PeerAdvertisement</A>&nbsp;rendezVous)</PRE>
<DL>
<DD>Sends advertisement about other RendezVous to a given peer
<P>
<DD><DL>
</DL>
</DD>
<DD><DL>
<DT><B>Parameters:</B><DD><CODE>destPeer</CODE> - is the advertisement of the peer to which to
 send the RendezVous advertisement.<DD><CODE>rendezVous</CODE> - is the advertisment of a RendezVous peer</DL>
</DD>
</DL>
<HR>

<A NAME="propagate(net.jxta.endpoint.Message, java.lang.String, java.lang.String, int)"><!-- --></A><H3>
propagate</H3>
<PRE>
public abstract void <B>propagate</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>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>
</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 abstract 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>
</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 abstract 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>
</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 abstract 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>
</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="isConnectedToRendezVous()"><!-- --></A><H3>
isConnectedToRendezVous</H3>
<PRE>
public abstract boolean <B>isConnectedToRendezVous</B>()</PRE>
<DL>
<DD>Return true if connected to a rendezvous.
<P>
<DD><DL>
</DL>
</DD>
<DD><DL>

<DT><B>Returns:</B><DD>true if connected to a rendezvous, false otherwise</DL>
</DD>
</DL>
<HR>

<A NAME="isRendezVous()"><!-- --></A><H3>
isRendezVous</H3>
<PRE>
public abstract boolean <B>isRendezVous</B>()</PRE>
<DL>
<DD>tells whether this rendezvous service currently acts as a "super-node"
 "rendezvous", knowlege hub, influence broker, or whichever higher
 status applies to the implementation.
<P>
<DD><DL>
</DL>
</DD>
<DD><DL>

<DT><B>Returns:</B><DD>boolean true if this rendezvous acts as a "rendezvous" per the
 implementation definition.</DL>
</DD>
</DL>
<HR>

<A NAME="walk(net.jxta.endpoint.Message, java.lang.String, java.lang.String, int)"><!-- --></A><H3>
walk</H3>
<PRE>
public abstract 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>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