On Wed, Feb 29, 2012 at 4:24 AM, Yanni Chiu <[email protected]> wrote:
> On 28/02/12 4:30 PM, Mariano Martinez Peck wrote: > >> >> If I understand you correctly, then what you are talking about is not >> caching objects but rather lazy loading. You mean when Glorp lets some >> proxies of the loaded graph so that they can load the rest of the graph >> later on? >> > > Okay, the concept I meant is lazy loading using proxies. > heheheh ok, then we agree :) Indeed, it would be nice to have that. What I am not sure is how to decide when and where to cut the graph and let some proxies. > > So what is "object cache" - i.e. what concept did you have in mind, when I > used the term "object cache" earlier? > > some internal optimization commonly done by ORMs (like Glorp) where they have a cache in primary memory of objects which were recently asked/queriered. The idea is to avoid going to the disk to fetch the object. -- Mariano http://marianopeck.wordpress.com
