cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Morrison, John" <John.Morri...@uk.experian.com>
Subject RE: Allowed Sitemap Constructs
Date Thu, 03 Jan 2002 13:15:57 GMT
> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> John Morrison wrote:
> > 
> > > From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> > > John Morrison wrote:
> > > > > From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> > > > > Another restriction we currently have is already entered 
> > > as a bug with
> > > > > the number 4357: An Action is not possible as a root 
> > > element inside
> > > > > a map:pipeline, only map:match can be a used as a 
> root element.
> > > > > So here again, is this by design?
> > > >
> > > > What would you expect the Action to do and when would you 
> > > expect it to do
> > > > it?
> > > >
> > > For example:
> > > <map:pipeline>
> > >   <map:act type="LogStatus"/>
> > > 
> > >   <map:act type="ProtectAllResource">
> > > 
> > >     <map:match pattern="docs/*">
> > >      ..
> > >     </map:match>
> > >   </map:act>
> > > 
> > > </map:pipeline>
> > > 
> > > So the actions are invoked immediately at the start of the sitemap
> > > processing,
> > > for example for any debugging or authentication or 
> > > initialization of the
> > > object
> > > model etc.
> > > 
> > 
> > The LogStatus I can understand, but won't the 
> "ProtectAllResource" slow
> > things down if the request doesn't match any of the patterns 
> > contained there
> > in?
> > 
> > Also, if you have multiple pipelines then the actions would 
> be invoked as
> > the request 'scans' them for the match...?  Is this what you want?
> > 
> Yupp, these both are intentionally! I think we should discuss 
> if this is a
> good example or not, but the restrictions itself ;-)
> 

I'm thinking that folks who try this won't expect the overheads it will
introduce.

Would it be acceptable for the sitemap transformation to take what you wrote
above and 'automagically' generate the following...

<map:pipeline>
 <map:match pattern="docs/*">
  <map:act type="LogStatus"/>
  <map:act type="ProtectAllResource">
  ...
  </map:act>
 </map:match>
</map:pipeline>

This would then allow you to 'group' matches within an action but would only
*do* the action when the match is found...?  Does this make sense?  Kind of
a compromise between the verbosity you want in the first instance and what
actually happens (my version...)?

J.


=======================================================================
Information in this email and any attachments are confidential, and may
not be copied or used by anyone other than the addressee, nor disclosed
to any third party without our permission.  There is no intention to
create any legally binding contract or other commitment through the use
of this email.

Experian Limited (registration number 653331).  
Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message