Hi, I am doing something like that. Our site is built up with functional blocks (top, categories, new contents...), representing the data from different api calls. What we do is to cache the api calls, we use a hash of the api call as the key and inside we store the response, usually xml or serialized objects.
It works great. On Fri, Oct 31, 2008 at 6:16 PM, MP <[EMAIL PROTECTED]> wrote: > > Hi, > > I've not used Memcached in my applications before; but I'm considering > it for my current project especially for its distributed nature. I > would like to get this group's help in formulating a right solution > based on their experiences in using Memcached . > > My application has a page (similar to igoogle, facebook etc) that has > many modules (Top News module, Group Photos, etc). Each module gets > its data from different data sources (all web services). All modules > show the most up-to-date data. Traditional way of implementing this > would be to generate html "fragments" for each module and cache it in > memory and serve it from memory on every request. > > If I were to use memcached (where memcache servers are different from > the app servers), then on every request I'll have make multiple > network calls (from app server to memcache servers) to fetch the > cached data. > > Has anyone used memcached for similar implementations? If so, is there > a better approach? Or is memcached not the right approach when we want > to fetch multiple caches on every page load? -- Juanse Pérez Herrero -- http://www.linkedin.com/in/juanseph
