Fix "phantom user" in discovery list
Occasionally, a user not currently online (or with different media threads from the online user) appears in the discovery list. The conjecture is that this may be due to user list content still present in an NDN content store. Need to determine the root cause and perhaps change content versioning strategy for this data. (Zhehao, you could correct this issue description?)
Updated by Zhehao Wang over 5 years ago
Jeff Burke wrote:
Occasionally, a user not currently online (or with different media threads from the online user) appears in the discovery list.
This is likely caused by restarting NDNCon and republishing audio. It's expected that the newly restarted user can discover itself until its old data times out. But Peter reported 5~10min before this (assumed) timeout happens. (Current data lifetime is 2 seconds, and 5 consecutive timeouts triggers a "leave" event)
@Peter, let's try to reproduce this at some point, meanwhile, seeing how the "deserialize" method of EntityInfo class's overloaded (and "onStateChanged" of the overloaded observer) could help. (If update channels of a user only happens when onStateChanged is called, this is indeed likely to happen. Essentially, different data with the same name (which is bad) does not trigger state updates from discovery library)