Provide a dojox.cache for generic client side caching functionality

[guest]

I've noticed with the rewrite of the dojox.grid that the model concept has been discarded in favour of the dojo.data store approach. The old grid model implemented caching on top of the store results. Now the model is gone, caching is left up to the store.

Since caching is also a generic piece of functionality (ie. doesn't have to be confined to a store), it would make sense to have a dojox.cache that could be utilized by a store, and also in other places that a user wants to cache data.

There is a javascript cache here that provides the caching functionality I was looking for...

​http://www.monsur.com/projects/jscache/

Perhaps the author could be contacted to allow this code to be added as dojox.cache.

[Adam Peller]

Jared, Bryan, your thoughts?

[Jared Jurkiewicz]

There was a few bits of work I had seen some time ago that were some folks attempts at building a caching store that just sat ontop of an existing datastore and cached the results. I should also try to dig that up and see if it makes sense to use. Both Snaplogic folks and some folks in IBM had a version.

[bill]

mark all (open) tickets w/blank milestones to be "tbd"; their milestones need to be set to a version number or to "future"

[Jared Jurkiewicz]

Need to get back to this. Targetting as future until enough time is available to look at this in depth.

[dylan]

The new Dojo Object Store introduced in 1.6 has a cache module. Closing this as complete.