Geoff Hutchison (ghutchis@wso.williams.edu)
Wed, 19 May 1999 21:40:46 -0400 (EDT)
On Wed, 19 May 1999, Andrew Scherpbier wrote:
> why it requires changes.
> Even if there are some things that cannot be done efficiently in the
> current format, the whole suite of programs in ht://Dig makes extensive
For the most part, the config format is very good. However, especially as
far as htdig is concerned (for indexing) there are some attributes that
would be useful to express on a per-server or per-URL basis. For example:
server_max_docs
server_wait_time
max_hop_count
(authentication--not really config file)
exclude_urls
limit_urls_to
.. etc.
> hashtable. I am just pointing out the fact that the impact of a format
> change could be much broader than it might first seem.
Exactly. And not only the structure of the config object, but the method
of accessing attributes. But it seems like allowing these attributes to be
accessed on at least a per-server basis would *really* help htdig. For the
rest of the programs, it really doesn't matter. I guess some people might
like per-server changes to htsearch, but that seems rather complicated.
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
htdig3-dev@htdig.org containing the single word "unsubscribe" in
the SUBJECT of the message.
This archive was generated by hypermail 2.0b3 on Wed May 19 1999 - 17:52:35 PDT