The results of this thread from my point of view can be found at
http://outerthought.net/wiki/Wiki.jsp?page=DesignPipelines.

Are there any other points?

Regards,
Reinhard

> -----Original Message-----
> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 14, 2002 8:57 AM
> To: [EMAIL PROTECTED]
> Subject: [SUMMARY] Pipeline match optimization (Re: [Q] Pipeline best
> practices)
>
>
>
> [EMAIL PROTECTED] wrote:
> > Another issue of having too  many pipelines.
>  > As i understand in the sitemap is generated into a java class.
>  > And the various matchers within a pipeline(s) are really a bunch
>  > of if-else if statements.
>  >
>  > So the more matchers you have (to match to a pipeline or
>  > various paths within a pipeline) your going to have a large
>  > series of if/else statements.  And... since this uses string
>  > compares and wildcards and... if there's alot of these if
>  > else if statements it will lead to performance issues.
> >
> > 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...
>
> Yes, and make search hierarchical.
> Since you can match inside a match, you can also do this.
>
> To get to match2-3 you need 8 matches
>
>    match1-1  |  1
>    match1-2  |  .
>    match1-3  |  .
>    match1-4  |  .
>    match1-5  |  .
>    match2-1  |  .
>    match2-2  |  .
>    match2-3  v  8
>
> But you can do:
>
>    match1      |  1
>      match1-1  !  x
>      match1-2  !  x
>      match1-3  !  x
>      match1-4  !  x
>      match1-5  !  x
>    match2      |  .
>      match2-1  |  .
>      match2-2  |  .
>      match2-3  v  5
>
> And have 5 matches
>
> --
> Nicola Ken Barozzi                   [EMAIL PROTECTED]
>              - verba volant, scripta manent -
>     (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> 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]>
>


---------------------------------------------------------------------
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]>

Reply via email to