JXTA in a Nutshell

JXTA Modules

JXTA has made the deliberate decision to specify mechanisms, rather than policies, for building P2P applications. For example, the JXTA platform implementation does not impose a unique search or authentication policy on JXTA developers. Each developer can specify the most appropriate authentication or search policies within the scope of his peergroups. Policies may be shared between peergroups when the same behavior is required. The JXTA peergroup framework provides the necessary mechanisms via the peergroup advertisement for developers to configure the set of policy behaviors used within each peergroup. The JXTA platform’s open-policy approach allows a multitude of behaviors for supporting a large variety of application domains. For instance, authentication policies for a financial-transaction peergroup are likely to be different than in a content-sharing peergroup, in which content accesses are free.

JXTA is designed to be independent of programming languages, system platforms, or service invocation models. JXTA embraces a heterogeneous world in which devices running different platforms and service invocation models can discover and interact with each other. Therefore, JXTA policy behaviors need to be described in an independent manner.

JXTA also believes in a dynamic world where peers can instantiate new policy behaviors as they interact with other peers and discover new peergroup behaviors. This viral effect enables peers to dynamically load and unload new ...