X-Git-Url: https://git.distorted.org.uk/~mdw/sgt/agedu/blobdiff_plain/05b0f827bf0178896f9484fe093fb0d99fa67ba2..522edd92f2bbef89ccd1dd0a3e874516fb47e2ef:/TODO diff --git a/TODO b/TODO index 4858350..c11cd11 100644 --- a/TODO +++ b/TODO @@ -1,31 +1,18 @@ TODO list for agedu =================== -Before it's non-embarrassingly releasable: - - - cross-Unix portability: - + use autoconf - * configure use of stat64 - * configure use of /proc/net/tcp - * configure use of /dev/random - * configure use of Linux syscall magic replacing readdir - + later glibcs have fdopendir, hooray! So we can use that - too, if it's available and O_NOATIME is too. - * what do we do elsewhere about _GNU_SOURCE? - - - tweak the short options. I think dump files should be a - second-class feature in general, so that --dump and --load should - be represented by capital options. That leaves -d free to be - --depth, which I think is more generally useful. - * while I'm tweaking the options list, "[all modes]" ought to - say "[most modes]", due to --scan-dump. - - - New mode: --remove, to destroy the data file. Handy for - totally self-contained usage: "-s . -w -R". - - - man page, --version. - -Future possibilities: + - 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 @@ -73,3 +60,16 @@ Future possibilities: 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.