*** empty log message ***

1 files changed, 26 insertions, 0 deletions

diff --git a/TODO b/TODO
index f30a612..a657694 100755
--- a/TODO
+++ b/TODO
@@ -12,6 +12,20 @@ correctness:
 	  lac_activity_cancel() from another thread. This could get
 	  hairy :-/
 
+	* Periodically stat /etc/resolv.conf and reload it if it has
+	  changed. (Though people will probably still think they have
+	  to restart even if they don't).
+
+	* consider 
+
+	  	   activity = lac_begin_activity (timeout);
+		   ...;
+		   lac_activity_wait(activity)/lac_activity_cancel();
+
+		   lac_end_activity(activity);
+
+	  within "..." you can call lac_activity_cancel();
+
 	* relative URI's
 		- showstopper for 1.0
 
@@ -33,6 +47,13 @@ correctness:
 		 - Accept it based on "Ok".
 
 misc:
+	* consider moving complexity from nameserver to query, ie.
+	  have the nameserver have one response function used for all
+	  replies. The nameserver would not keep the map between 
+	  queries and reply functions.
+		We would have to have that map in the query file, 
+	  but it may not be that bad since we already have a table
+	  of outstanding queries there.
 	* need a real regression test suite
 	* get rid of CacheRecord->type
 	* Cleanup of the DNS module
@@ -52,6 +73,11 @@ misc:
 	    data anyway.
 
 performance:
+	* With an unstable network connection, DNS packages will often
+	  get lost. We should probably be a little more aggressive about
+	  requerying. For example resending every .5 second under the
+	  assumption that with a well-working network, the response
+	  will usually arrive well within .5 seconds.
 	* figure out when exactly the write buffer should be flushed in the
 	  http module.