From 9988112c87bc5e4ad39880ffd2aa898e0e62e82f Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Thu, 28 Sep 2006 23:57:44 +0000 Subject: r8973@Kushana: nickm | 2006-09-28 16:53:19 -0400 Refactor entry guard status logic a lot; allow more factors [like not having a Guard flag or being listed in ExcludeNodes] to render a guard "unlisted" (now called "unusable"); track guard down status (now called "unreachable") separately from is_running. svn:r8519 --- doc/TODO | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/TODO b/doc/TODO index 5e3289cd67..b3fe48b8a0 100644 --- a/doc/TODO +++ b/doc/TODO @@ -24,8 +24,9 @@ x - When we've been idle a long time, we stop fetching server until we've fetched correct ones. x - If the client's clock is too far in the past, it will drop (or just not try to get) descriptors, so it'll never build circuits. -N - when we start, remove any entryguards that are listed in excludenodes. -N - Remember the last time we saw one of our entry guards labelled with + o when we start, remove^Wmark as unusable any entryguards that are listed + in excludenodes. + o Remember the last time we saw one of our entry guards labeled with the GUARD flag. If it's been too long, it is not suitable for use. If it's been really too long, remove it from the list. o Figure out avoiding duplicate /24 lines -- cgit v1.2.3-54-g00ecf