On May 12, 2009, at 2:47 PM, Neil Curzon wrote:
I think it should be possible to reason about the web framework independently from the back end.
However it just ain't so. If the front-ends had equivalent architectural impact, then sure. Or if everything were serial, then sure. However, a front end can behave differently with minimal back- end activity vs. a high degree of back-end activity, simply because it may be able to work or cache work product in one scenario that isn't possible in the other, or where the margins are so tight that such effort is a higher percentage of the total work done. Real end-to-end performance on a request is subject to a lot of architectural constraints, when it comes to measuring, and you can't do a straight- line computation from a no-op case.
For example, the design of T5 may be such that a page constructed with a lot of javascript from different components is handled better than with taglibs, since T5 can bundle it up, call it a versioned asset, send it as one single compressed stream, and cache it on the client. If the other framework handles the JS file-by-file, without compression, and has to re-fresh more frequently, then it's possible that T5 can vastly outperform the other in a complex application, by design.
cheers, Christian Edward Gruber christianedwardgru...@gmail.com http://www.geekinasuit.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
