by cdshearer >> Tue, 26 Mar 2002 21:48:17 GMT
OK, perhaps I should have given some context to what I'm using this for...
I'm using the cache for many small-ish (a few hundred objects at most) collections of lookup objects that are used to populate ComboBox and ListBox controls. The collections are very rarely updated but likely to be frequently read. Caching the collections on the client, particularly in an Application Server environment will eliminate the need to go to the database to lock the collection when it's used to populate the controls. Additionally, the controls register for notifications on the cached collection rather than the persistent one so the notifications are transient, and don't involve the database server.
We also have the concept of effective date ranges for these lookups, so loading the collection into the control involves more that just attaching the collection to the control as it needs to be filtered based upon the current date. For this reason, we effectively do the filtering once per day for all clients. We expect that this will make the solution more scalable, not less!!!
I agree though that the solution wouldn't be appropriate for every collection - there are some that are too large or update too frequently for the technique to be of any benefit.
Craig