On Tue, 15 May 2001, Glenn Nielsen wrote:
> I would like to propose that the new Jasper require jdk 1.2.
> The current version of jasper can be used by those who have jdk 1.1.x.
> Then we don't have to worry about jumping through hoops trying to
> get the new jasper to run both in 1.1 and 1.2, plus we can optimize
> for 1.2. In addition JSP 1.2 will require jdk 1.2 or greater.
+1 for the generator.
+1 for the runtime implementation
My only -1 is for the method signatures in the runtime - but that
should be a tiny problem, and I'll watch and fix in case something slips
by.
The idea is that I want to have an alternate implementation that uses only
JDK1.1 ( or J2ME ) - this is not a big priority, but it can't hurt anyone
to keep a door open.
I don't care too much about JDK1.1 - but it's very important for me to
have a way to use a runtime that works in more restricted environments
( but that will not be the "default" - I can make such a think somewhere
outside - as long as we don't add something in the signatures that would
prevent that )
I already ordered the tini board - and it supports only JDK1.1 so far, so
please don't try to make me change the vote :-)
Costin
>
> Regards,
>
> Glenn
>
> [EMAIL PROTECTED] wrote:
> >
> > > Jasper performance has already been identified as an area needing
> > > improvement.
> > >
> > > Discussions and work on this has already started in the main tomcat
> > > branch in CVS jakarta-tomcat/proposals/jasper34, but this may be
> > > moving to the CVS repository jakarta-tomcat-jasper.
> > >
> > > This work just started recently, I don't know when it will be ready.
> >
> > It will take few months - it's not that easy.
> >
> > We already added tag pooling in tomcat3.3, and that have a significant
> > effect on performance if you are using tags - but that's just the
> > beginning.
> >
> > The first step is to reorganize the code. Then we'll try to make the code
> > generator more customizable ( probably by using XSLT for some of the
> > operations ). The real performance enhancement will come when we start
> > tunning the generated code - there are many ideas around, but we need the
> > refactoring first.
> >
> > BTW, jasper will share most of the code for the 1.1 and 1.2 APIs, so all
> > enhancements will be available in both 3.x and 4.x ( and other containers
> > as well ).
> >
> > If you have ideas, code or opinions - please get involved, we need you :-)
> >
> > Costin
> >
> > >
> > > Rickard Öberg wrote:
> > > >
> > > > Hi!
> > > >
> > > > We are using Tomcat/JBoss and are pleased with the actual functionality.
> > > > What is killing us right now is the performance of the code generated by
> > > > Jasper, especially when using taglibs in complex ways. The generated
> > > > code is way too unoptimized.
> > > >
> > > > So, if this has not been asked before (in which case a RTFA is ok,
> > > > although I've looked already), my question is:
> > > > When will Jasper be rewritten?
> > > > Are there any such projects underway now?
> > > > Have there been any discussions about this yet?
> > > > Am I the only one seeing this problem, or are more people concernced
> > > > about it?
> > > >
> > > > Thanks,
> > > > Rickard
> > > >
> > > > --
> > > > Rickard Öberg
> > > > Software Development Specialist
> > > > xlurc - Xpedio Linköping Ubiquitous Research Center
> > > > Author of "Mastering RMI"
> > > > Email: [EMAIL PROTECTED]
> > >
> > >
>
>
