--- [EMAIL PROTECTED] wrote: > It may help to break things up with sub site maps to > help limit the searching. > > Or put the most likely pipelines to get hit first > and the least likely last... >
After reading Stefano's thread on dev (?) regarding the profiling work he did revealing that matching may be the most expensive operation, I've been thinking along these exact lines. The second one certainly seems to be the easiest to apply. Seems like search algorithm ideas apply here too - you want to get to a match in the least number of decisions possible, so either subsitemaps, or nested matchers seem the best ways to implement a good decision tree. Seems like laying out url space can help this. Question: wouldn't in theory subsitemaps carry more overhead than nested matchers? Of course there are many reasons to use them any way but this would be a factor in deciding when. I don't see any benefit (besides different configurations as mentioned) of multiple pipeline sections, unless each one has a small number of top level matchers that can help eliminate all options quickly. Geoff Howard __________________________________________________ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
