some ejb implementations do this for you, as long as the pstore is 'owned'
by the ejb server.
> -----Original Message-----
> From: Rick Gibbs [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, September 23, 1999 8:19 AM
> To: [EMAIL PROTECTED]
> Subject: JSP-EJB and caching
>
> We are in the process of implementing a JSP-EJB solution and I had an
> idea that might help increase the performance of our application and
> wanted to see what people thought.
>
> Our application is very read intensive and the data is updated on a
> limited basis. What I would like to do is implement a caching system
> on the JSP side. The cache would store summary objects that were a
> result of some query. When an item was updated via an EJB, a message
> would be sent out to the cache marking it as dirty so then next time it
> was accessed it would access the EJB. This way any access to the data
> would be in memory and would speed up actions such as sorting.
>
> Does anyone see any potential problems with this approach?
>
> Thanks
>
> Rick
> _________________________________
> Rick Gibbs
> earthcars.com, Inc.
> [EMAIL PROTECTED]
> http://earthcars.com
>
> ==========================================================================
> =
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
