Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#184 burst and burst_ack status not propagated

u2.10.12
pending
Entrope
Server (143)
5
2012-06-01
2010-04-12
wiebe
No

In a netburst, the burst and burst_ack status of servers is not propagated (this happens when 2 or more servers link on the net at the same time). This means the status of servers shown in MAP and STATS v is not correct. A simple fix for this could be to indicate such status with server flags (e.g. b for burst and a for burst_ack).

Discussion

  • G3rrlt
    G3rrlt
    2010-10-23

    afaik there are already flags for that (although they aren't propagated) or am I wrong? STATS v atleast can show them.

     
  • Entrope
    Entrope
    2012-06-01

    • milestone: --> u2.10.12
    • assigned_to: nobody --> entrope
    • status: open --> pending
     
  • Entrope
    Entrope
    2012-06-01

    Burst status is propagated by using J instead of P in the protocol version number (sent in s_serv.c, parsed in m_server.c). Burst ack status is mostly of local interest. If there's a compelling reason to track BurstAck servers across the network, we can consider adding that; otherwise, I am inclined to leave it as is.