From d76d0493d64c512e36e1bd1d3b9e9aaf73f7df1e Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Thu, 19 Jun 2008 04:50:06 +0000 Subject: start sending "COUNT=%d RECOMMENDATION=%s" key/values on bootstrap problem status events, so the controller can hear about problems even before tor decides they're worth reporting for sure. svn:r15357 --- doc/TODO | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'doc/TODO') diff --git a/doc/TODO b/doc/TODO index d43a7f632..bb729af13 100644 --- a/doc/TODO +++ b/doc/TODO @@ -340,15 +340,17 @@ R - investigate: it looks like if the bridge authority is unreachable, o directory authorities shouldn't complain about bootstrapping problems just because they do a lot of reachability testing and some of it fails. -R - if your bridge is unreachable, it won't generate enough connection +R * if your bridge is unreachable, it won't generate enough connection failures to generate a bootstrap problem event. R - if "no running bridges known", an application request should make us retry all our bridges. -R - get matt to fix vidalia so it moves to a "starting tor" bootstrap + o get matt to fix vidalia so it moves to a "starting tor" bootstrap state if it hasn't gotten any status events. Maybe it can even be more certain by checking the version (<0211) and/or looking at the results of the getinfo. -R - in circuituse.c, +R - get matt to make vidalia do a getinfo status/bootstrap-phase to + get caught up after it connects. +R * in circuituse.c, /* XXX021 consider setting n_conn->socket_error to TIMEOUT */ For 0.2.1.x: -- cgit v1.2.3