JXTA in a Nutshell

JXTA ID Types

JXTA IDs may refer to many types of resources: pipes, peers, etc. Each JXTA ID format type may support references to one or more of these resource types.

Other types may be defined. Each of the individual ID types may provide additional requirements specific to its type.

Peergroup IDs

Peergroup IDs refer to peergroups. A peergroup ID should canonically, uniquely, and unambiguously refer to a peergroup.

Every ID format must support this ID type because all of the other ID types refer to the peergroup to which they belong, and it must support encoding of the World Peergroup, but support for other peergroups is optional.

For example, suppose you are defining an ID format for peer IDs based on a driver’s license number. Drivers’ licenses are not organized into groups. This can be considered equivalent to all drivers’ licenses belonging to the same group: the global World Peergroup.

Peer IDs

Peer IDs refer to peers. A peer ID should canonically, uniquely, and unambiguously refer to a peer. Support for this ID type is optional.

If a JXTA binding recognizes the ID format, it should be able to extract a peergroup ID from a peer ID. This peergroup ID identifies the peergroup of which the peer is a member.

Codat IDs

Codat IDs refer to codats. A codat ID should canonically, uniquely, and unambiguously refer to a codat. This ID type is optional. ID formats are not required to implement it. If a JXTA binding recognizes the ID format, it should be able to extract a peergroup ...