NSIS-ka
A free C++ implementation of NSIS protocols

Changeset 4487


Ignore:
Timestamp:
Sep 24, 2009, 5:44:18 PM (8 years ago)
Author:
stud-lenk
Message:

Refresh timing revisited: The only TODO is in handle_response_in_established()

File:
1 edited

Legend:

Unmodified
Added
Removed
  • ntlp/branches/20090723-multicast/src/ntlp_statemodule_querier.cpp

    r4485 r4487  
    419419                         << r_entry->get_min_peer_rs_validity_time() << " ms");
    420420        remaining_responses_time = r_entry->get_min_peer_rs_validity_time();
    421         // TODO MULTICAST: shorten running timer for to_Refresh_QNode
    422421      }
    423422      if (remaining_responses_time == 0) {
     
    566565                        << r_entry->get_min_peer_rs_validity_time() << " ms");
    567566      remaining_responses_time = r_entry->get_min_peer_rs_validity_time();
    568       // TODO MULTICAST: shorten running timer Refresh_QNode
    569567    }
    570568    if (remaining_responses_time == 0) {
     
    753751
    754752  // start Refresh_QNode again
     753  // TODO MULTICAST:
     754  // Only re-start timer if it would run shorter than the old one. Otherwise a
     755  // malicious peer could send RESPONSE messages before the QN has sent a QUERY
     756  // which causes this timer to be restarted. This in turn causes the next
     757  // QUERY to be sent *after* the other peer's RS validity timeout
     758  // (assumed they have the same RS validity time), and hence would effectively
     759  // cause the other peers to drop out (by missing refreshing QUERY).
    755760  starttimer(r_key, r_entry, refresh_qnode, 0, randomized(refresh_timeout, gconf.getpar<float>(gistconf_retryfactor)));
    756761
Note: See TracChangeset for help on using the changeset viewer.