A capsule is a combination of a packet and its forwarding routine;
the forwarding routine is executed at every active node the
packet visits in the network.
Stats request capsules look like:
4 Address of the root of the tree
4 Unique key id of this request tree
2 Application port
1 Depth
4 Time capsule was sent
Return capsule looks like:
4 Address of the actual source of the information
4 Address of the node that requested stats from source node
4 Time capsule this is a response to was sent
4 Latency (0 if latency has yet to be figured)
4 Number of nodes the source of this return sent to
Stats request capsules look like:
4 Address of the root of the tree
4 Unique key id of this request tree
2 Application port
1 Depth
4 Time capsule was sent
4 Cachetime parameter
4 Returnwait parameter
4 Returntimeout parameter
Return capsule data looks like:
4 Address of the actual source of the information
4 Address of the node that requested stats from source node
8 Time capsule this is a response to was sent
8 Latency (0 if latency has yet to be figured)
8 The key id of this capsule (used in the node cache)
4 Number of nodes the source of this return sent to
4 Cachetime parameter
n The addresses of the nodes the request was sent to
n The byte array containing the return data
Mobile protocol definition - The protocol involves two types of capsules,
one for carrying actual data, and one for updating forwarding information
on routers.
Mobile update capsule processor - This will update forwarding information
on routers so that MobileCapsules can direct themselves to the proper
destination
A runtime error thrown when an application or capsule tries
to get the address of the node it is executing on, and there
is no address yet defined for the node.
This application transverses the network, starting with the node
it is run from and returns statistics from all reachable nodes
within a specifiable depth
This application transverses the network, starting with the node
it is run from and returns statistics from all reachable nodes
within a specifiable depth
An Xdr instance encapsulates an external, byte-oriented data
structure (an "External Data Representation".) Xdr's can include
Strings, byte arrays, booleans, bytes, shorts, ints, longs,
TypeIDs.
This documentation is Copyright (C) 1998-2001 The University of Utah and the University of Washington. All Rights Reserved. See the individual source files for distribution terms. Documentation, software, and mailing lists for ANTS v2.0 can be found at the Janos Project: http://www.cs.utah.edu/flux/janos/