Project JXTA

Package net.jxta.impl.id.binaryID

The 'binary' format is a general purpose JXTA ID Format.

See:
          Description

Class Summary
BinaryID A BinaryID is a 256-byte, identifier.
BinaryIDFactory A BinaryIDFactory generates a BinaryID id.
CodatBinaryID This class implements a Pipe ID.
DigestTool This is a utility class used to create pipe advertisement named and BinaryID for the pipeID to create a private address space that can be hosted in the public discovery system or sent over unencrypted channeds without revealing their intent or purpose.
IDFormat The 'BinaryID' format is a general purpose JXTA ID Format.
Instantiator ID Factory for the binary ID type.
ModuleClassBinaryID This interface defines a Module Class Identifier.
ModuleSpecBinaryID A ModuleSpecID uniquely identifies a particular network behaviour (wire protocol and choregraphy) that may be embodied by a Jxta Module.
PeerBinaryID This class implements a PeerID.
PeerGroupBinaryID This class implements a PeerGroup ID.
PipeBinaryID This class implements a Pipe ID.
 

Package net.jxta.impl.id.binaryID Description

The 'binary' format is a general purpose JXTA ID Format. It implements Peer, group, and pipe ID types. The remaining types are supported, but not guarenteed (CODAT not supported at all yet).

The DigestTool class is probably the main entry point for most developers. The class creates various BinaryID types with an SHA digest hashing. The intent is to make secure but non-random possible for ID pipes, peers, and peer groups. When using the utility, it is recomended tha you use a hash size apropriate to your address space.

Author:
Daniel Brookshier turbogeek@cluck.com
See Also:
This package supports the creation of an identifier given a binary value that is 0 to 255 bytes long that is encoded as Base64. The value needs to be a unique value so that it can be used for addressing peers, pipes, and groups.

The implementation also includes the creation of a digest hash given an arbirary length string. This allows you to encode any type of data into a secure digest. The digest hash is recomended unless you are sure that your binary id is truely unique. Using a digest hash is also preferrable for situatins when you have an id that could be comprimized if known (like a socal security number). The digest tools also have convenience methods for mixing an id with a function name and a way to create a time limited ID.

Note that this ID currently only allows parent peer group ID to be of type UUID.

, JXTA Protocols Specification : IDs


JXTA J2SE