On Tue, 8 Jun 1999, Ray Cromwell wrote:
> I don't see how caching Bean return values solves your problem.
It allows us to check cache validity at fixed periods, rather than at
(possibly inappropriate) intervals such as page requests or session
creations. I agree that there are plenty of cases this won't handle, but
I believe caching would significantly increase the solution coverage of
JSP from where it is now -- in a way our application seems to need.
> About 1.5 years ago, I wrote an RMI/Servlet application server that used
> an RMI server to handle managing objects and caches. The way I solved the
> problem was by enforcing that all SQL calls went through a manager object
> which would invalidate any cached objects that were dependent on DB data
> that got modified via insert/update/delete.
Yes, this is basically the solution I've taken (modelled on the GSP
implementation).
Marc Hedlund <[EMAIL PROTECTED]>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
