Mike Cannon-Brookes wrote:
If you read the whole email you'd know why. Let me quote:
"But it's a dangerous option, since it may not be apparent that this
slowdown will occur. If possible, configuration of actions should not
occur this way."
Given the huge amount of reflection in webwork anyway, is a little more
going to hurt?
Well, that's the whole point! I want to somehow reduce reflection,
because it's bad for performance. If you haven't noticed WW isn't
exactly a speed-demon. And it could/should be.
(And as someone said - wouldn't it all be cached anyway?)
You can cache the methods, but there's still the actual reflection
overhead (+type conversion).
PS I'm +1 for action parameters - v. useful!
Even though there's overhead and security problems with it?
/Rickard
--
Rickard Öberg
[EMAIL PROTECTED]
Senselogic
Got blog? I do. http://dreambean.com
-------------------------------------------------------
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
