Greetings, Does anyone think that ht://Dig may be suffering from feature bloat? Some of the bugs I'm finding indicate that lots of the features aren't being used. An example is that limit_normalized checks the same form (usually unnormalized) of the URL (usually unnormalized) as limit_urls_to, and limit_urls_to checks the normalized form of start_url. (Before I commit the fixes to those bugs, could someone else please verify that they really are bugs, and I'm not just missing something?)
Given that several people commented on how slow digging now is, should we look at reducing the feature set for future releases? That will: a) Increase the speed b) Reduce memory consumption c) Reduce the testing required d) Reduce the amount of code which must be maintained e) Reduce the potential for conflicts of combinations of features. Just a thought... Lachlan -- [EMAIL PROTECTED] ht://Dig developer DownUnder (http://www.htdig.org) ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
