Ignore:
Timestamp:
Jul 28, 2008, 7:47:16 PM (13 years ago)
Author:
charles
Message:

rename `pulse' as peerPulse() and trackerPulse() to make backtraces easier to read

File:
1 edited

Legend:

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

    r6406 r6412  
    6868
    6969    PEX_INTERVAL            = (90 * 1000), /* msec between sendPex() calls */
    70     PEER_PULSE_INTERVAL     = (50),        /* msec between pulse() calls */
     70    PEER_PULSE_INTERVAL     = (50),        /* msec between peerPulse() calls */
    7171    RATE_PULSE_INTERVAL     = (250),       /* msec between ratePulse() calls */
    7272
     
    836836
    837837static int
    838 pulse( void * vmsgs );
     838peerPulse( void * vmsgs );
    839839
    840840static int
     
    15461546didWrite( struct bufferevent * evin UNUSED, void * vmsgs )
    15471547{
    1548     pulse( vmsgs );
     1548    peerPulse( vmsgs );
    15491549}
    15501550
     
    16461646
    16471647static int
    1648 pulse( void * vmsgs )
     1648peerPulse( void * vmsgs )
    16491649{
    16501650    const time_t now = time( NULL );
     
    19231923    m->info->have = tr_bitfieldNew( torrent->info.pieceCount );
    19241924    m->state = AWAITING_BT_LENGTH;
    1925     m->pulseTimer = tr_timerNew( m->handle, pulse, m, PEER_PULSE_INTERVAL );
     1925    m->pulseTimer = tr_timerNew( m->handle, peerPulse, m, PEER_PULSE_INTERVAL );
    19261926    m->rateTimer = tr_timerNew( m->handle, ratePulse, m, RATE_PULSE_INTERVAL );
    19271927    m->pexTimer = tr_timerNew( m->handle, pexPulse, m, PEX_INTERVAL );
Note: See TracChangeset for help on using the changeset viewer.