Information Technology Reference
In-Depth Information
For example, to a user in an MIR system, he/she
may have no interest in the fact that a “publish to
network” command involves flooding the super
peers to connect with a suitable rendezvous for
publication using UDP with NACK enabled reli-
ability, but still he/she may understand well that a
publish will make their information available to
others on the network. The GAP is this high level
view, whereas the configuration of the network
designers will specify the low-level details of
how this happens.
Currently there are three GAP bindings
implemented:
registry and the Web Service Invocation
Framework (WSIF), or indeed run on top
of P2PS to host Web services within a P2P
environment.
•
JXTA
: the original GAP Interface bind-
ing was to JXTA, which has been not bee
updated, and superceded by P2PS.
In DART, we are interested in forming un-
structured P2P networks and therefore need to
employ technologies that can adapt and scale
within such an environment. We therefore, use
the GAP interface and employ the use of the P2PS
middleware binding to achieve this goal. P2PS is
described in the next section.
•
P2PS:
a lightweight Peer-to-Peer middle-
ware.
P2P Simplified
•
Web Services:
allows applications to dis-
cover and interact with Web and WS-RF
Services—using WSPeer, which can use
standard Web-based tools, such as a UDDI
For distribution across dynamic networks, we use
the P2PS binding. Peer-to-Peer Simplified (P2PS)
Figure 4. The GAP interface provides a middleware independent interface for developing P2P applica-
tions, whilst the GAT provides access to Grid tools and middleware.
Search WWH ::
Custom Search