Berin Loritsch wrote:
> > The real question is: are those unmatched action useful in real life?
>
> Yes. Here are two examples:
>
> 1) Themed Site
> The Action will determine what theme to apply to the site (I did this using
> session to maintain the theme once the user selected it). Currently, I have
> that Action as the root of every single <map:match> in the sitemap. It would
> be more usefull to have this:
>
> <map:act type="theme-selector">
> <map:match>...</map:match>
> <map:match>...</map:match>
> <map:match>...</map:match>
> <map:match>...</map:match>
> </map:act>
>
> 2) Authenticated Site
> It would be useful (especially for child sitemaps) to have an authentication
> action happen before any protected resource can be selected. In many corporate
> webapps, the entire site must be protected.
Makes perfect sense.
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?
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
