Shall I keep old-style (pre 0.5) actions in the code? A comment in
HTTPContent.py by Ian says that they have gone anyway. The 0.9 release
may be a good opportunity to get rid of them completely. This old
stuff may be confusing for new users.
Hmm... I can't remember just what they are. I think the code should
stay as it is until after 0.9. If "old style" actions mean _action_=foo
(as opposed to _action_foo), I think we should keep that indefinitely,
as it's still useful. But I think there were some other slight
differences to the pre-0.5 algorithm, and those are turned off by
default, so that can go.
You're right, we need to be more precise.
"Very old style" actions:
_action_=foo calls methodNameForAction(foo)()
"Old style" actions:
_action_=foo calls foo()
"New style" actions.
_action_foo calls foo()
I was actually talking about "Very old style actions".
To use them, you have to set OldStyleActions = True in
Application.config which is by default False since version 0.6.
Since by default, methodNameForAction(foo)==foo,
very old style actions are identical to old style actions unless you
explicitely override the methodNameForAction method.
If we want to keep "old style" actions indefinitely (and I think that's
fine), why not allow "very old style" as well and get rid of the
confusing OldStyleActions setting in Application.config?
I see no security or compatibility problem in doing so, but it would
simplify a lot.
-- Christoph
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Webware-devel mailing list
Webware-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/webware-devel
