[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
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
Or put the most likely pipelines to get hit first and the least likely
last...
That can be problematic if your most used pipelines are the generic matches.
Eg, three special cases and 100 general cases:
match=fee.foe
match=fee.fie
match=fee.fum
match= fee.*
To be honest, I circumvented this whole issue by having as few pipelines as possible.
Basically I use action or event id's that point to metadata files. The metadata files
have all the information how to build a portal page, I then use WSUI (wsui.org) files
to describe each of the portlets.
Can you share your pipeline.
Maybe you organize your content in a much smarter way than I can imagine.
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, October 14, 2002 3:59 PM
Subject: Re: [Q] Pipeline best practices
To be honest, I circumvented
Hi Ivelin,
-Original Message-
From: Ivelin Ivanov [mailto:[EMAIL PROTECTED]]
Sent: Sunday, October 13, 2002 4:25 PM
To: [EMAIL PROTECTED]
Subject: [Q] Pipeline best practices
For example how many pipelines in a sitemap are reasonable?
How do one chooses when to put multiple
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)
--- [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
