On Wed, 3 Apr 2002, Kin-Man Chung wrote:

> It's great that you are doing performance evaluation for different versions
> of tomcat.  Can your jstl run in tc3 and tc4 without change?  Can we
> separated performance attributed to containers as opposed to those attributed
> to jasper?  For those jasper performance, how can we identify the most
> profitable improvements that we should do?

Jasper is pretty easy to embed in a container - the current jasper4 
depends on few servet2.3 calls, easy to substitute with old ones and make 
it run in 3.3.

The only problem is 'disabling' the JSP1.2 functionality - i.e. have a 
setting to request it to throw exception if it detects a feature that 
shouldn't be used.

This will be usefull for jsp1.3 as well - if you want to use a single 
codebase for all jsp versions.

Costin




> 
> - kin-man
> 
> > Date: Wed, 03 Apr 2002 07:29:32 -0500
> > From: peter lin <[EMAIL PROTECTED]>
> > Subject: Jasper2
> > To: Kin-Man Chung <[EMAIL PROTECTED]>
> > MIME-version: 1.0
> > Content-transfer-encoding: 7bit
> > X-Accept-Language: en-US
> > 
> > 
> > hi kin-man,
> > 
> > I was planning on checking your latest jasper2 today/tomorrow and
> > compare it against tc3.3 jasper and tc4.0.3 jasper.
> > 
> > which branch should I check out to grab jasper 2.  As part of my own
> > research, I was planning on writing a complete dynamic website for
> > managing personal photo-albums using scriptlets, beans and jstl.  that
> > way I have the same exact site implemented three different ways for
> > performance evaluation.
> > 
> > thanks
> > 
> > peter
> > 
> > 
> > 
> > Kin-Man Chung wrote:
> > > 
> > > I plan to work on jasper performance, especially those related taglibs.
> > > But I want to clean up jasper first, before I tackle the performance.
> > > 
> > > Are you convinced that tag pooling is the answer?  First you have the
> > > cost of monitor locks; then you also need to go thru hashtable to find
> > > the tag from the pool (I assume that's how it works here), and this
> > > is cheaper than calling the tag constructor?  Can you do some measurements?
> > > 
> > > I think we should attack the iteration tags first.  If we can move the
> > > loop invariants out of the loop, we would have solved the tag reuse
> > > problem.
> > > 
> > > If you are interested in jasper performance, I'd be very glad to work
> > > together with you; but let make sure that jasper2 is stable first.
> > > 
> > > Thanks.
> > > 
> > > > Date: Tue, 02 Apr 2002 11:37:35 -0500
> > > > From: peter lin <[EMAIL PROTECTED]>
> > > > Subject: Jasper2
> > > > To: Kin-Man Chung <[EMAIL PROTECTED]>
> > > > MIME-version: 1.0
> > > > Content-transfer-encoding: 7bit
> > > > X-Accept-Language: en-US
> > > >
> > > >
> > > > hi kin-man,
> > > >
> > > >
> > > > I was planning on porting the tag pool in jasper 3.3 to tomcat 4, until
> > > > someone mentioned you're working on jasper 2.  Are you planning on
> > > > adding tag pooling?  if you are, I can help port the tag pooling to it.
> > > >
> > > >
> > > > peter lin
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> 
> 


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to