Subject: [htdig3-dev] differences in local_urls_only action between 3.1.4 & 3.2.0b1
From: Gilles Detillieux (firstname.lastname@example.org)
Date: Wed Feb 23 2000 - 09:33:14 PST
Hi, folks. I'm in the process of looking over all changes to 3.1.x
since last September, to make sure that all 3.1.x changes make it
into the next 3.2 beta. I've found differences in the handling of
the local_urls_only attribute between 3.1.4 & 3.2.0b1. In 3.1.4,
I set it up such that local_urls_only only disables the fallback to
HTTP for files that fall in the scope of local_urls or local_user_urls.
In 3.2.0b1, Geoff was working in parallel with me, but set it up such
that it disables any HTTP or other protocols for all URLs, whether in
the scope of local_urls or local_user_urls or not.
What do all of you think is preferable? On the one hand, the name does
seem to imply that only local urls should be dug, so Geoff's approach
does make sense. However, my approach gives you more flexibility in that
you can combine local-only digging of one site with non-local digging
of another, and still allows completely local digging if the scope of
local_urls encompases the whole scope of start_url and limit_urls_to.
As far as I can tell, the change affects one line of code, and three
documentation entries, so it's pretty trivial. I just wanted some
feedback on the clarity vs. flexibility tradeoff, rather than just
changing it to do it my way. Thanks.
-- Gilles R. Detillieux E-mail: <email@example.com> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil Dept. Physiology, U. of Manitoba Phone: (204)789-3766 Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------ To unsubscribe from the htdig3-dev mailing list, send a message to firstname.lastname@example.org You will receive a message to confirm this.
This archive was generated by hypermail 2b28 : Wed Feb 23 2000 - 09:36:48 PST