JXTA in a Nutshell

Rendezvous Protocol

The RVP is responsible for propagating messages within a JXTA peergroup. While different peergroups may have different means to propagate messages, the RVP defines a simple protocol that allows them to:

• Propagate messages and receive propagated messages

• Control the propagation of messages (TTL, loopback detection, etc.)

Behavior

RVP introduces the notion of special peers, called rendezvous peers. Rendezvous peers have the extra capability of repropagating messages they received. Peers can dynamically become a rendezvous peer and/or dynamically connect to a rendezvous peer. Some secure peergroups may impose security restrictions on which peers can become rendezvous peers, and on which rendezvous a peer may connect to.

The connection between a peer to a rendezvous peer is achieved by an explicit connection associated with a lease. The connection is established by sending a lease request message to a rendezvous peer using the peer endpoint message service.

Each rendezvous peer is listening on a specific endpoint address with the following service name and parameter:

service name: JxtaPropagate 
service param: PeerGroup ID

Messages

The RVP defines the following set of messages in order for a peer to establish a connection to a rendezvous peer:

LeaseRequest

This request is sent by a peer desiring to connect to a given rendezvous. No lease amount has to be requested by the peer; the rendezvous will allocate whatever amount is appropriate. A lease can always ...