More work towards making bridge users able to connect via bridges:

  - demand options->Bridges and options->TunnelDirConns if 
    options->UseBridges is set.
  - after directory fetches, accept descriptors that aren't referenced by
    our networkstatuses, *if* they're for a configured bridge.
  - delay directory fetching until we have at least one bridge descriptor.
  - learn how to build a one-hop circuit when we have neither routerinfo
    nor routerstatus for our destination.
  - teach directory connections how to pick a bridge as the destination
    directory when doing non-anonymous fetches.
  - tolerate directory commands for which the dir_port is 0.
  - remember descriptors when the requested_resource was "authority", 
    rather than just ignoring them.
  - put bridges on our entry_guards list once we have a descriptor for them.
    When UseBridges is set, only pick entry guards that are bridges. Else
    vice versa.


svn:r10571

1 files changed, 10 insertions, 1 deletions

diff --git a/doc/TODO b/doc/TODO
index 34338790a..ba19a4fa0 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -219,10 +219,19 @@ Things we'd like to do in 0.2.0.x:
       D Do we want to maintain our own set of entryguards that we use
         after the bridge? Open research question; let's say no for 0.2.0
         unless we learn otherwise.
-      - Ask all directory questions to bridge via BEGIN_DIR.
+      o if you don't have any routerinfos for your bridges, or you don't
+        like the ones you have, ask a new bridge for its server/authority.
+      . Ask all directory questions to bridge via BEGIN_DIR.
+        - use the bridges for dir fetches even when our dirport is open.
 N     - Design/implement the "local-status" or something like it, from the
         "Descriptor purposes: how to tell them apart" section of
         http://archives.seul.org/or/dev/May-2007/msg00008.html
+      - timeout and retry schedules for fetching bridge descriptors
+      - give extend_info_t a router_purpose again
+      - react faster to download networkstatuses after the first bridge
+        descriptor arrives
+      - be more robust to bridges being marked as down and leaving us
+        stranded without any known "running" bridges.
     - Bridges operators (rudimentary version)
       - Ability to act as dir cache without a dir port.
       o Bridges publish to bridge authorities