Patrick Lightbody wrote:
Ok. Well, if the performance overhead is so negligble as some suggest, then maybe it's ok. Can't say I like it though, for mentioned reasons.So then how would the situation outlined below work then? I understand the deployment-settings vs. business login parameter issue, but where would those kinds of parameters be set? I don't think in the HTML URL would be a good idea. I like being able to make two different alias names that are similar (same class) but behave differently based on "settings".
Plus, iff it's put into an interceptor then people like me can remove it :-)
/Rickard
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
