Ignore:
Timestamp:
Dec 11, 2008, 5:02:34 PM (12 years ago)
Author:
charles
Message:

(libT) add some documentation about the three separate peer structs and how they are related.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/libtransmission/peer-mgr.c

    r7353 r7357  
    9797};
    9898
    99 /* We keep one of these for every peer we know about, whether
    100  * it's connected or not, so the struct must be small.
    101  * When our current connections underperform, we dip back
    102  * into this list for new ones. */
     99/**
     100 * Peer information that should be kept even before we've connected and
     101 * after we've disconnected.  These are kept in a pool of peer_atoms to decide
     102 * which ones would make good candidates for connecting to, and to watch out
     103 * for banned peers.
     104 *
     105 * @see tr_peer
     106 * @see tr_peermsgs
     107 */
    103108struct peer_atom
    104109{
Note: See TracChangeset for help on using the changeset viewer.