Berin Loritsch <[EMAIL PROTECTED]> writes: <snip/>
> For this reason, providing a generic cache that works on > whole resources is a much more efficient use of time. For > example, it would make my site run much more efficiently if I > could use a cache for my database bound objects instead of > creating a call to the database to re-read the same > information over and over. Allowing the cache to have hooks > for a persistence mechanism will allow it to handle > write-back style caching for user objects. Write-back caches > will asynchronously write the information to the persistence > mechanism while the critical computation path is minimally affected. Ahh, good point. In the intermediate results cache (DTM like database) that I envision that would definitely be something I'd expect (but forgot all about)...
