Re: tapestry plugs...

Have you done any performance testing of you application (or a prototype of the 
application)?  Even with the marginal costs of using Tapestry, I doubt the 
presentation layer is your bottlneck, it tends to be excessive communication 
between layers (and excessive transactions) or inefficient database access.

Like the man Knuth:  beware of false optimizations.  Using Tapestry could give 
you extra time in your development to fix the real bottlenecks.

Dig up a copy of The Java Report, Sept 2001.  There's an article on Tapestry 
that compares the performance of JSPs and Tapestry on an application using a 
shared back end.  The perfomance graph was virtually identical, up until server 
saturation, where JSP had a slight edge.  

Since then, Tapestry has changed and improved quite a bit; some things are now 
more efficient, in other areas there have been sacrifices to reduce the load on 
developers.

--
[email protected]

http://tapestry.sf.net
> 
> Interesting stuff, still I'm concerned about performance.
> If I was building a web app for a company (ie a non
> internet app), this would be the tool.
> 
> BTW, how do you set cookies in Tapestry? I saw the getCookie,
> but no setCookie.
> 
> Dru Nelson
> San Carlos, California
> 
> 
> 


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf