Command flow in p2pSB

1. User issues command (ie. ConnectToNetwork)
2. Service host looks up the appropriate service.  In this case, ConnectToNetworkService.
3. Execute is triggered on the ConnectToServiceObject.
4. AvailablePeers are retrieved, and ConnectToNetworkMessage delivered to each by the following process.  Note that Redezvous Servers are considered peers in this list.
5. The list of known transport types for each peer is identified from the PeerConnectionInfo class associated with the peer.
   
6. ConnectToNetworkMessage is sent to each peer via that transport.  Note that this is an asyncronous action and considered fire and forget.
7. The message is places in the message store for correleation of connect messages.

1. ConnectToNetworkMessage is received by a listener.
2. Decrement TTL, and if 0 dispose of message.
   
3. Message is routed to the message node.  Message node "touches" the message.
   
4. Message node routes it to the ConnectToNetworkService.
5. Connect to network service acknowledges the message with a response back through the incoming message node.
6. An entry in the peer list is made for this node.
   
7. The message is forwarded to all peers on this servers peer list that are not already on the visited peers list.

Technorati Tags: p2pSB