[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] r9242: Change TODO item so we can make a tricky decision later rath (in tor/trunk: . doc)
- To: or-cvs@xxxxxxxxxxxxx
- Subject: [or-cvs] r9242: Change TODO item so we can make a tricky decision later rath (in tor/trunk: . doc)
- From: nickm@xxxxxxxx
- Date: Tue, 2 Jan 2007 16:47:10 -0500 (EST)
- Delivered-to: archiver@seul.org
- Delivered-to: or-cvs-outgoing@seul.org
- Delivered-to: or-cvs@seul.org
- Delivery-date: Tue, 02 Jan 2007 16:47:17 -0500
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-cvs@xxxxxxxxxxxxx
Author: nickm
Date: 2007-01-02 16:47:04 -0500 (Tue, 02 Jan 2007)
New Revision: 9242
Modified:
tor/trunk/
tor/trunk/doc/TODO
Log:
r11796@Kushana: nickm | 2007-01-02 15:37:45 -0500
Change TODO item so we can make a tricky decision later rather than an incredibly tricky one now.
Property changes on: tor/trunk
___________________________________________________________________
svk:merge ticket from /tor/trunk [r11796] on c95137ef-5f19-0410-b913-86e773d04f59
Modified: tor/trunk/doc/TODO
===================================================================
--- tor/trunk/doc/TODO 2007-01-02 20:58:30 UTC (rev 9241)
+++ tor/trunk/doc/TODO 2007-01-02 21:47:04 UTC (rev 9242)
@@ -80,8 +80,9 @@
o clients don't log as loudly when they receive them
o they don't count toward the 3-strikes rule
D But eventually, we give up after getting a lot of 503s.
-N - Delay when we get a lot of 503s, rather than punting onto the
+ D Delay when we get a lot of 503s, rather than punting onto the
servers that have given us 503s?
+N - Add a 'BadDirectory' flag to statuses.
- authorities should *never* 503 a cache, and should never 503
network status requests. They can 503 client descriptor requests
when they feel like it.