Timeout mechanism - Githubissues

almgong / NDNOverWifiDirect

1 stars 0 forks source link

Timeout mechanism #31

Closed almgong closed 7 years ago

almgong commented 7 years ago

one issue: if the other peer closes their NFD app before the timeout occurs, then the NFD will end up automatically destroying the face towards this other peer, and the current device will never be able to correctly refresh its state (create a new face towards the other peer on probe interest). This is because to the NDNController on the current device, there still exists state information about the previous connection (as timeout did not occur as expected).

almgong commented 7 years ago

No good solution for this problem yet...

almgong commented 7 years ago

This problem does not occur as long as the user leaves the NFD app for at least as long as the max timeout time. So we could either assume this to be the case, or we will need to have a background thread routinely check for inconsistent state.

The latter is possible, since we can just enumerate Faces using Nfdc.getFaceList(...), and then check remote uris for consistency with NDNController's peersMap.

almgong commented 7 years ago

merged with #34