Re: Profiling Tapestry

On Thursday 19 December 2002 23:20, Howard M. Lewis Ship wrote:
> Hm.
>
> That might be an area to look into.  Since all Tapestry output is run
> through IMarkupWriter .... we don't absolutely have to base it on a
> PrintWriter.  Still, if we read templates as bytes, we'd have to do a lot
> of our own conversion back to char just to parse the damn thing.  I guess
> the templates start as binary, convert to char, and convert back to binary
> on the way to the browser.
>


There is a new O'Reilly article that talks about "Servlet Best Practices" in 
which the overhead of using PrintWriter is discussed and a solution is 
presented:

http://www.onjava.com/lpt/a/2825

The case they talk about is just serving a file, and not doing much else with 
it, so I don't know how usefull the article is for Tapestry, but a 50% 
improvement[1] is kind of cool :-)




Best regards,
Luis Neves

[1] - in the best case




-------------------------------------------------------
This SF.NET email is sponsored by:  The Best Geek Holiday Gifts!
Time is running out!  Thinkgeek.com has the coolest gifts for
your favorite geek.   Let your fingers do the typing.   Visit Now.
T H I N K G E E K . C O M        http://www.thinkgeek.com/sf/