> From: Sylvain Wallez [mailto:[EMAIL PROTECTED]] > > Stefano Mazzocchi a écrit : > > > > Berin Loritsch wrote: > >
<examples of useful unmatched actions from Berin go here> > > Ok, I think Berin identified the need for unmatched actions, now, let's > > get a little deeper, please, answer these questions: > > > > do you see the need for 'pre/post' matching actions? > > > > do you see the need for 'intra-matching' actions? > > Another criteria that should be taken in to account is : does the action > have pipeline-building children or not ? Please, do not use such criteria. Empty actions could be useful also. Say, you have product catalog sub-sitemap: <!-- high precedence URL patterns --> <map:match>...</map:match> <!-- process request parameters productId=xxx&addToComparison=yes --> <map:act type="add-to-comparison"/> <map:act type="product-selection"> <map:generate/> <map:serialize/> </map:act> <!-- low precedence URL patterns --> <map:match>...</map:match> Example might be not perfect, but it gives an idea... > > The "theme-selection" action above can be either pre/intra/post-matching > depending on the precedence order of URL patterns. An intra-matching > example : > > <!-- non-themed high precedence URL patterns --> > <map:match>...</map:match> > > <!-- themed URL patterns --> > <map:act type="theme-selection"> > <map:match>...</map:match> > <map:match>...</map:match> > </map:act> > > <!-- non-themed low precedence URL patterns --> > <map:match>...</map:match> > > With this new criteria : > +1 for pre/intra/post-matching non-empty actions > +1 for pre-matching empty actions : this can be used to setup some > application-level context Fully agree with you here. > -0 for intra/post-matching empty actions : I don't see any real > usefullness for them. May be you can change your mind at least for +0? ;) Vadim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
