You could probably make a lot of headway on something like this using existing technologies. Serialization for example. If an object impelements serializable (in java), then the caching mechanism could hold it in memory, remember how long it has been since the last access and then serialize to disk when it hasn't been accessed in a long time.
In a way, as well, the OS handles a lot of this with virtual memory on a page by page basis. If you have a web app that caches a lot in application state, it'll grow in memory size and then start swapping out that app to disk when it gets stale.
It's a good idea. Programming tends toward laziness so lazy caching is probably almost definitely going to happen. Isn't this kind of what memcache is? Couldn't memcache automatically let go of some of its cached queries?
In a way, as well, the OS handles a lot of this with virtual memory on a page by page basis. If you have a web app that caches a lot in application state, it'll grow in memory size and then start swapping out that app to disk when it gets stale.
It's a good idea. Programming tends toward laziness so lazy caching is probably almost definitely going to happen. Isn't this kind of what memcache is? Couldn't memcache automatically let go of some of its cached queries?