X-Git-Url: https://git.distorted.org.uk/~mdw/sgt/agedu/blobdiff_plain/9c6e61f23dd65086378606be16d3740d909477d4..1f651677c857d752bc477c937a80a9a3ada5aff4:/TODO

diff --git a/TODO b/TODO
index 0cd19f8..f8c723d 100644
--- a/TODO
+++ b/TODO
@@ -1,13 +1,18 @@
 TODO list for agedu
 ===================
 
-Future possibilities:
-
- - integrate more usefully with the output of configure. It's
-   generating oodles of automatic boilerplate in config.h and I'm
-   sure three quarters of it _ought_ to be usable to add
-   portability, if only I had the gumption to actually pay attention
-   to all those HAVE_FOO macros it's defined for me.
+ - we could still be using more of the information coming from
+   autoconf. Our config.h is defining a whole bunch of HAVE_FOOs for
+   particular functions (e.g. HAVE_INET_NTOA, HAVE_MEMCHR,
+   HAVE_FNMATCH). We could usefully supply alternatives for some of
+   these functions (e.g. cannibalise the PuTTY wildcard matcher for
+   use in the absence of fnmatch, switch to vanilla truncate() in
+   the absence of ftruncate); where we don't have alternative code,
+   it would perhaps be polite to throw an error at configure time
+   rather than allowing the subsequent build to fail.
+    + however, I don't see anything here that looks very
+      controversial; IIRC it's all in POSIX, for one thing. So more
+      likely this should simply wait until somebody complains.
 
  - IPv6 support in the HTTP server
     * of course, Linux magic auth can still work in this context; we
@@ -49,9 +54,27 @@ Future possibilities:
       Unclear what the right UI would be on Windows, too;
       command-line exactly as now might be considered just a
       _little_ unfriendly. Or perhaps not.
+       * Disk scan procedure: the FindFirstFile / FindNextFile
+	 functions to scan a directory automatically return the file
+	 times along with the filenames, so there's no need to stat
+	 them later. Would want to fiddle the shape of the
+	 abstraction layer to reflect this.
     + Alternatively, a much easier approach would be to write a
       Windows version of just the --scan-dump mode, which does a
       filesystem scan via the Windows API and generates a valid
       agedu dump file on standard output. Then one would simply feed
       that over the network connection of one's choice to the rest
       of agedu running on Unix as usual.
+
+ - it might conceivably be useful to support a choice of indexing
+   strategies. The current "continuous index" mechanism' tradeoff of
+   taking O(N log N) space in order to be able to support any age
+   cutoff you like is not going to be ideal for everybody. A second
+   more conventional "discrete index" mechanism which allows the
+   user to specify a number of fixed cutoffs and just indexes each
+   directory on those alone would undoubtedly be a useful thing for
+   large-scale users. This will require considerable thought about
+   how to make the indexers pluggable at both index-generation time
+   and query time.
+    * however, now we have the cut-down version of the continuous
+      index, the space saving is less compelling.