Last updated at 5:32 pm UTC on 3 March 2005
When AardWorks Gossip needs to send a packet to another peer, the local peer list is first checked whether that peer is in the table and has hopCount=1. If this is the case, the packet is sent directly to the UDP host:port associated with the peer.
hopCount=1 tests that we previously exchanged information with the peer. Formally it only checks whether we have received information from the peer. But this means at least that a) the peer was there, b) it hasn't yet been declared 'dead' because it didn't respond timely to a peer list exchange request, and c) we have a UDP host:port that we observed ourselves. All in all, if the peer is still alive, we'll have a very good chance that the packet will arrive.