The nav is not determined by the user so there is no need to store it in each user
session I would say. The database is hit to create these JSPs actually before tomcat
is even started up, so there is no cost in doing that.
Cheers ADC
-----Original Message-----
From: LILES, DAVID (CONTRACTOR) [mailto:[EMAIL PROTECTED]
Sent: Thu 08/04/2004 20:35
To: Tomcat Users List
Cc:
Subject: RE: My own caching implementation...
Not to get too wrapped up in "how-to"... since you are already going to the
database to identify the nav links for the person, was there a reason why you didn't
put the results into a collection and save it to session for the user? That way they
are always available during their session. When you display the page all you have to
do is iterate through the collection to display the nav links.....
Just a thought....
-----Original Message-----
From: Allistair Crossley [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 08, 2004 2:28 PM
To: Tomcat Users List
Subject: RE: My own caching implementation...
I don't think you understood quite what I meant - my JSP beforehand was
actually dynamically creating all the nav from the database per request. All I mean by
"cache" in this case is that I wrote a script that goes through the database tree and
generates loads of little JSPs so that they do not have to be calculated from the DB
at runtime. I am sure Jasper caches these small JSPs.
Cheers! ADC
-----Original Message-----
From: John Trollinger [mailto:[EMAIL PROTECTED]
Sent: Thu 08/04/2004 17:55
To: 'Tomcat Users List'
Cc:
Subject: RE: My own caching implementation...
Jasper 2 already caches jsp pages. Have you realy noticed a
performance
increase?
-----Original Message-----
From: Seth Newton [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 08, 2004 11:35 AM
To: Tomcat Users List
Subject: Re: My own caching implementation...
Yeah, that'd be my first guess.....set development to false.
Why didn't you just try it? It would have taken you just as long to
try
it as it did for you to write an email and send it.
----- Original Message -----
From: "Allistair Crossley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 08, 2004 11:25 AM
Subject: My own caching implementation...
> Hi Guys
>
> I have been trying to improve the performace of our app the past week
> and
one of the things I did was to cache our vast navigation systems as
lots
of JSPs each with the page ID as the jsp filename.
>
> Annnyway, this works fine but each time a page is accessed where the
> JSP
include for the navigation has not been used before there is a 3 second
delay or so where presumably the include is compiled because thereafter
it is fast. Cool.
>
> Now, a moment ago we pre-released a version to technical staff and
> what we
saw was that even pages that had been visited seemed after 5 clicks on
them to re-compile?
>
> I am just wondering if Tomcat will compile these include fragments
> again
for some reason? Should I be using development=false in the Jasper
sevlet in servlet.conf to stop this happening??
>
> Cheers Guys, ADC
>
>
> <FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE>
> -------------------------------------------------------
> QAS Ltd.
> Developers of QuickAddress Software
> <a href="http://www.qas.com";>www.qas.com</a>
> Registered in England: No 2582055
> Registered in Australia: No 082 851 474
> -------------------------------------------------------
> </FONT>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
