You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by David LAGARDERE <dl...@yahoo.fr> on 2002/08/20 10:36:17 UTC
Pipelineand matchers
Hello.
Is it better to have as many pipelines as matchers or
is it recommended having one pipeline including all
matchers ? What are the technical differences ? What
are the consequences in terms of performances ?
Thanks in advance.
David LAGARDERE
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: Pipelineand matchers
Posted by Vadim Gritsenko <va...@verizon.net>.
David LAGARDERE wrote:
>Hello.
>
>Is it better to have as many pipelines as matchers or
>is it recommended having one pipeline including all
>matchers ?
>
Split as you want. Usually, you have at least two pipelines: one
internal and one is not. In the future (2.1), you will be able to choose
pipeline implementation - then, you may have internal/external and
caching/noncaching combos.
>What are the technical differences ?
>
It was mentioned already on this list and somewhere else.
1. Internal or not
2. Pipelines can have different exception handling
3. In future: choose different pipeline implementations.
> What
>are the consequences in terms of performances ?
>
One pipeline is a bit faster then many.
Vadim
>Thanks in advance.
>
>David LAGARDERE
>
>
---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>