controversial; IIRC it's all in POSIX, for one thing. So more
likely this should simply wait until somebody complains.
- - it would be useful to support a choice of indexing strategies.
- The current system's 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 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.
-
- IPv6 support in the HTTP server
* of course, Linux magic auth can still work in this context; we
merely have to be prepared to open one of /proc/net/tcp or
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.
~mdw / sgt / agedu / blobdiff