Re: Profiling Tapestry

"Luis Neves" <[email protected]> Wed, 20 Feb 2002 01:05:09 -0000

Newsgroups	gmane.comp.java.tapestry.contrib
Message-ID	<001e01c1b9aa$a59c3020$6401a8c0@2KP2020>

On Thursday, December 19, 2002 11:20 PM,
"Howard M. Lewis Ship" <[email protected]> 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.

How does XMLC solves the issue? They are doing
something similar to what Tapestry does, but more efficiently.


> How is this different than JSP?  Most of the JSP implementations put the
> template into strings and have endless out.print("....") statements.

I am not sure that I understand you on this, but Resin doesn't do that.
Resin takes the template and does something like this:

jsp_string = "\r\n<HTML>\r\n<BODY>\r\n".getBytes();

and then writes the jsp_string to a OutputStream.

Best regards,
Luis Neves




-------------------------------------------------------
This SF.NET email is sponsored by: Geek Gift Procrastinating?
Get the perfect geek gift now!  Before the Holidays pass you by.
T H I N K G E E K . C O M      http://www.thinkgeek.com/sf/