One of the possibilities I was discussing with Phil yesterday was to
implement freemarker caching on the WW side of things--just like we do
with OGNL. In WW if we're not in devMode, then I think its safe to say
that we can read the template once and never reread it. This would
eliminate the need to move the ftl files out of the jars and also
eliminate the penalty of not having an ftl files in your own custom
theme. This could (should) also be moved in struts2 as well. That
way, in non-devMode we would get the best performance we can, out
-of-the-box. (It certainly would have saved me a lot of effort--that
was where all of our performance woos came from)
Tom
Ted Husted wrote:
Even though this is for WW, almost all of it is applicable to Struts 2.
This is a key phrase. There are a lot of very successful WW
deployments out there, with the same performance levels.
We really need to setup our own benchmarks, so that we can run them
with the templates deployed. I'd love to do this myself, but I'm
totally time-deprived right now.
Eventually we'll move this to S2 and update it, but so few people are
using Struts 2 right now, I think this is adequate.
That's going to change quite quickly. Even though we're still in beta,
people are already posting jobs for S2. Even though the benchmarks
might not tell the whole story, narrowing the cycles would make it
easier for more people to adopt S2 (And hopefully some of those will
lend us a hand. Even with the merge, we still don't have more active
committers than we had a year ago.)
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
