>
> 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?
>
We are using a similar approach and so far things look okay in the integration
test (touch wood)
The only difference we have to your approach is that instead of having a message
sent to the cache to mark it as dirty, we send the new data to it. Access to the
cache is controlled by using a multiple reader / single writer lock so that all
the readers get consistent data.
Manoj.
===========================================================================
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".
