The OGNL performance increase doesn't do anyone any good if the rest of WebWork is too unstable to upgrade to. First things first. Stablize the current code in CVS. Then work on new features.

Hani Suleiman wrote:

Well, the ognl stuff seems very promising, how about having it implemented on a
branch (say, OGNL_1 or something), with a view to integrating it once others
have had a look and feel it's worthwhile?

Again, I stress that the goal for adding it (from my perspective at least) is
performance. There should be NO configuration changes, and absolutely NO
external changes. The only different (hopefully) will be superior performance on
the branch version. If it ends up being ugly/unusable/slow/unfashionable, the
branch can merrily die off, if it's useful/pretty/a positive step, it can land
on HEAD. Any objections?



-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork




-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to