Table | Caption |
---|---|
2.1 | Conceptual models for information exchange |
2.2 | Main OS/2 Peer Networking components |
3.1 | Major p2p implementations examined in detail in this book |
4.1 | Summary of security issues in p2p communication contexts |
4.2 | Summary of security issues in p2p sharing contexts |
6.1 | ICQ component summary, common to many IM implementations |
6.2 | Header fields present in ICQ v5 protocol |
6.3 | Client to server commands current in ICQ v5 protocol, packets sent encrypted |
6.4 | Server to client commands current in ICQ v5 protocol, sent not encrypted |
6.5 | AIM component summary, very similar to ICQ |
6.6 | Jabber component summary |
6.7 | Namespaces supported for the Jabber message “x” and “iq” element |
7.1 | Gnutella component summary, as realized in current popular client implementations for file sharing |
7.2 | Some current Gnutella-clone clients for different platforms |
7.3 | Ideal relationship of potential reach to the parameters connected nodes (N) and value of message TTL |
7.4 | Gnutella Network Protocol v0.4 descriptors |
7.5 | The header fields in any Gnutella v0.4 descriptor |
8.1 | Mojo Nation component summary |
8.2 | Distributed Mojo Nation services that manage the network and earn Mojo. In the aggregate, they implement the distributed network agents. |
8.3 | Message structure in Mojo Nation |
8.4 | Messages for building and maintaining the network |
8.5 | Block search, retrieval and publication, with content tracking |
8.6 | Relay messages |
8.7 | Payment messages |
8.8 | Swarmcast component summary |
9.1 | Component summary for Freenet |
9.2 | Summary of defined message header types and expected response types in client (FCP) and node (FNP) communication with a Freenet server node. Exact header names vary between different documentations. |
9.3 | Summary of defined message header types for (FNP) communications between Freenet server nodes. Exact header names vary between different documentations. |
9.4 | Summary of defined message header field types in Freenet messages. Numeric values are expressed in hexadecimal. |
10.1 | Groove component summary |
10.2 | JXTA component summary |
10.3 | JXTA core projects |
10.4 | JXTA services projects |
10.5 | JXTA application projects |
12.1 | Comparison between different types of trust certificates seen on networks |
18.220.136.165