Re: Caching of read-only DB contents in an EJB

[Lahooti, Hamid]

"Laird, Nelson" wrote:
> A cache needs to be kept in sync with its data source.
> For that you need update notifications generated by
> data source.

>>Horsefeathers.
Do horses have feathers in your planet?

>>Write-through caches solve this problem nicely without
>>requiring that the underlying data source perform any notifications
>>whatsoever.
Ya sure. Go ahead and implement a write through cache that works
cross multiple VMs with full transactional control and while you're
at it, change the legacy applications so they write to the cache
instead of the database. Ah, almost forgot, write your own container.
I wish I worked for an education establishment and have the
luxury of having all the time in the world.

Cheers
Hamid

===========================================================================
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".