Stefano Mazzocchi wrote:
>
> 3) make it illegal to have intra-matching actions
>
> [the option of allowing intra-matching actions is, IMO, wrong by design]
>
> 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.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
