The easiest approach is to retrieve all the content for later pages in the
Action for the first page. This would slow the first page, but would allow
later pages to be pulled from cache. This seems like the easiest approach.
It could be accomplished using a course-grained Entity Bean or some
.
Additional input is well appreciated.
Thanks,
Dean Chen
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 03, 2002 10:33 AM
To: Struts Users Mailing List
Subject: Re: Loading Database
The easiest approach is to retrieve all the content for later
]
To: 'Struts Users Mailing List' [EMAIL PROTECTED]
cc:(bcc: Kevin Bedell/Systems/USHO/SunLife)
Subject: RE: Loading Database
Thanks this will help alot. Our application is not based on EJB, rather
using straight forward JavaBeans. However, I assume there can be a lot of
performance gains in using EJB
This is what I am doing and it greatly improves responsiveness. I put an
initialization servlet in the load-on-startup in web.xml and it loads Maps
and Lists of application (context)-level data into memory. Any user needed
that data (like a List of cities or a Map of zipcodes and markets) then
4 matches
Mail list logo
