[mnet-devel] open issue in v0.6.2: how to deal with unreliable peers?

[Zooko Ozoko]

This issue is registered in the Issue Tracker:

http://sourceforge.net/tracker/index.php?func=detail&aid=845178&group_id=43482&atid=436453

[ 845178 ] do we ever stop trying former peers?

 I've noticed that my node keeps trying to send messages
 to nodes that it knew long ago, but that have long
 sinced stop responding.

 Is there any feature in there to make it prefer nodes
 who currently respond ??

 I'm not entirely sure that there is.

 UnreliableHandicapper *ought* to mark non-responding
 nodes as unreliable, so that they get discriminated
 against in the future.

 I'm not sure if it is currently doing this.

 Even if it *is*, that raises the issue of, what happens
 when a node returns to service after a few days of
 absence? He will be considered as "unreliable" by his
 peers. Will they ever try him again?

 This could cause chronic failures in a large,
 high-churn network.

 I guess we'll find out...

 If I have time I will investigate those two questions...


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
mnet-devel mailing list
mnet-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mnet-devel