Then again, if you use jikes or some other *fast* compiler to compile the
jsp, the performance may actually be decent.
Scott
-----Original Message-----
From: James Duncan Davidson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, March 23, 1999 8:04 PM
Subject: Re: servlet and JSP
>> The solution to this would be to change GNUJSP from a servlet
>> to a filter. The Jetty architecture can easiy handle this as it
>> is based around a stack of handlers, some of which may be filters.
>> Other WWW servers such as Jigsaw have similar architectures.
>>
>> Now that you've prompted me, I'll be looking into doing this
>> for the combination of Jetty/GNUJSP.
>
>Caution -- big performance lag ahead -- if you feed the raw JSP to a
>filter that compiles it and returns the results to a client, you'll be
>soaking lots of time in javac. JSP isn't a good tool to use for dynamic
>code generation....
>
>.duncan
>
>___________________________________________________________________________
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff SERVLET-INTEREST".
>
>Archives: http://archives.java.sun.com/archives/servlet-interest.html
>Resources: http://java.sun.com/products/servlet/external-resources.html
>LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
