Jockey Peer Bridge Interface (PBAPI) Design |
The peer bridge interface acts as an adapter framework for peer network implementations, to allow peer network implementations to be embedded in a server framework that is exposed using the standard peer interface (PI) API.
Each peer network implementation (such as JXTA, Gnutella, Jabber) normally exists as an isolated network of peers, using heterogenous protocols and divergent network abstraction APIs. The peer bridge framework allows these networks to be viewed as a single unified meta-net, with a unified API. The unified peer bridge API (PBAPI) is translated into the appropriate peer network messages and protocols by a pluggable peer network implementations.
The first collection of classes in the PBAPI provide interfaces for a peer network implementation to register itself with the framework and provide basic network discovery and lookup.
PBNetManagerFactory | Related Classes |
---|---|
|
PBNet PBNetManager |
PBNet | Related Classes |
---|---|
|
PBAbstractNetManager PBNetManager |
PBAbstractNetManager | Related Classes |
---|---|
|
PBNetManager PBNetManagerFactory |
PBNetManager | Related Classes |
---|---|
|
PBAbstractNetManager PBNetManagerFactory |
PBAbstractDirectory | Related Classes |
---|---|
|
PBAbstractNetManager PBFindMarker |
PBDirectory | Related Classes |
---|---|
|
PBFindMarker |
PBFindMarker | Related Classes |
---|---|
|
PBDirectory PBAbstractDirectory |
PBDirectoryListener | Related Classes |
---|---|
|
PBDirectory |
The next collection of classes implement a messaging framework for peer applications.
In this API, a messenger handles the exchange of messages with the peer network. Messengers are specific to a peer group. (For more information about peer groups, see the Domain Concepts section.)
PBMessenger |
Related Classes |
---|---|
|
PBAbstractMessenger PBPeerGroup |
PBAbstractMessenger | Related Classes |
---|---|
|
PBMessenger PBPeerGroup |
The PBAPI fully supports synchronous and asynchronous messages. Asynchronous message calls return a marker, which acts as an IOU for the message transfer. The message listener interfaces provide the mechanism for peer networks to notify the Jockey framework of the presence of new messages, requests, or responses that must be handled.
PBMessage | Related Classes |
---|---|
|
PBAbstractMessage |
PBAbstractMessage | Related Classes |
---|---|
|
PBMessage |
PBMessageReceiver | Related Classes |
---|---|
|
PBMessenger |
PBMessageSender | Related Classes |
---|---|
|
PBMessenger |
PBSendMarker | Related Classes |
---|---|
|
PBMessage |
PBReceiveMarker | Related Classes |
---|---|
|
PBMessage |
PBResponseMarker | Related Classes |
---|---|
|
PBMessage PBSendMarker |
The final set of classes in the PBAPI show the relationships between the domain objects in the peer framework.
PBPeerEntity | Related Classes |
---|---|
|
PBAbstractPeerEntity | Related Classes |
---|---|
|
PBPeerEntity |
PBPeerGroup | Related Classes |
---|---|
|
PBAbstractPeerGroup | Related Classes |
---|---|
|
PBPeerGroup |
PBPeer | Related Classes |
---|---|
|
PBAbstractPeer | Related Classes |
---|---|
|
PBPeerEntity |