linuxdcpp-team team mailing list archive

[poy <855315@xxxxxxxxxxxxxxxxxx>]

there is no SUP identifier corresponding to the AP / VE split because it
is considered to be backwards-compatible: old clients / hub lists keep
working fine, with the exception of that one information that they now
get wrong. users can update their client if they want to see accurate
information after the AP / VE split; hub lists are assumed to be active
so they should update in time as well.

if you believe this is not backwards-compatible enough, and want to add
a SUP id for this split, i'd advise moving this discussion to adcportal.

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to ADCH++.
https://bugs.launchpad.net/bugs/855315

Title:
  AP extention implantation

Status in ADCH++:
  New

Bug description:
  The latest rev's are not anouncing the AP extention in their SUP and
  are sending the INF including AP(if its received from the connecting
  client) to all clients, regardless they have it in SUP or not and
  causing missing  information in the userlist for older clients.

  Same counts for the PING also there is no verification if the pinger
  supports AP, and receives a new style AP and VE field regarding the
  hubsoft making ADCH to be a "unknown" hubsoft, and offcourse the
  pinger also receives a mixed userlist with INF's containing AP and not
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/adchpp/+bug/855315/+subscriptions