According to Lachlan Andrew: > Even if it is not causing Chris's problem, I've been thinking for a > long time that this re-parsing may partially account for the big > slowdown in digging with recent 3.2.0 betas. From speaking with > Gabriele, I know that he finds the feature very useful. However, I > can't find the config file format documented, so I don't think that > many people can benefit from it, and it is currently just > (unquantified) bloat. > > If Chris finds that that is in fact the problem, I suggest that: > 1. We set a flag if per-host attributes are used at all > 2. If no per-host attributes are used, all expensive-to-parse > attributes (like regular expressions) should be cached in their > parsed forms.
Remember that there are URL blocks as well as server blocks and globals, so we actually have 3 different levels. It might be useful to maintain a status for each attribute that tells us the lowest level at which the attribute is defined. That way even if some attributes are used in URL blocks, we don't need to reparse the ones that aren't. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
