> -----Oorspronkelijk bericht----- > Van: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Namens Rob Vermeulen > Verzonden: dinsdag 9 augustus 2005 13:35 > Aan: Discussion list for developers > Onderwerp: Re: [Developers] cache release strategy framework > (second run) > > > Hi Ernst, > > I read your proposals about improving MMBase caching. It > sounds interesting. Enriching MMBase events with information > about which field has changed sounds good. I have my doubts > about old / new values of fields (this can have high > penalties if fields become very large).
Twoo things made me think i could do this: 1 very large fieds are not stored in nodes if i'm correct, so they won't be stored completely as old values 2 the 'old value' fields are cleaned after the node is committed. so it is overhead, but not overly much (i think) and memory is not realy a problem anymore, is it? I could be wrong about this, becouse i am not totaly shure about what is stored in nodes and what not. It is definitely a point that needs to be cleard up. > > I also like the idea of having strategies for caching. As you > pointed out you will need different caching implementation > upon different web applications. I encourage having admin > pages to monitor caches which can be (un)plugged live. > > Maybe we could brainstorm, or simply hear what you have to > say, on a next developers meeting. I hope to see a Caching > project soon :-p i will post a project proposal this afternoon Ernst > > greetings Rob Vermeulen > _______________________________________________ > Developers mailing list > [email protected] > http://lists.mmbase.org/mailman/listinfo/developers > _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
