Okay, realizing there are all sorts of types of caching I'll try to be more precise,
I mean backend caching. For example the result from clusterbuilder queries. When calling getClusterNodes(query) I would want a query to be executed only if the data in the database has changed. Otherwise, 99.99% times, it should give me a cached result, sothat the query is not absorbing too much processing time. Is this possible, or do I have to use a mechanism that tells the clouds on the multiple servers that data has changed and the clusternodes should be retrieved again? And what about cloud.getNode() or nodeManager.getNodelist(), do they always execute the query or can they give me a cached result? Paul ----- Original Message ----- From: "Michiel Meeuwissen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 22, 2004 10:57 AM Subject: Re: caching > Paul van Beukering wrote: > > I'd like to use caching in my mmbase app. > > Accept for the API I can't find an example or documentation for this > > subject. > > Can someone tell me where I can read about this? > > What do you want to cache? Most MMBase caches itself are automaticly used, > you probably don't even need to look at the API to use it in your mmbase > app. You may want to change some sizes perhaps (witch caches.xml). > > Caching possibilities on the front-end which are often used are a caching > front-proxy (which may need you to set certein http header, which can be > arragned by <mm:content expires="<time>") or oscache (see > www.opensymphony.com).. > > > Michiel > > > -- > Michiel Meeuwissen mihxil' > Mediacentrum 140 H'sum [] () > +31 (0)35 6772979 nl_NL eo_XX en_US > > > >
