I haven't looked much at CherryPy's cache filters. My goal is to create a website that can expand with user load. I need to be able to add extra web servers, running my application, when load required it. I therefore follow the shared-nothing architecture.
http://en.wikipedia.org/wiki/Shared_nothing_architecture memcached is, amongst other things, a central point of caching for load-balanced web servers. If you tried to use CherryPy's filters in the same situation, you'd end up with a local cache on each web server, and they'd all be out of sync. Which would make your application suck. memcached isn't so hard, it simply acts as a dictionary, storing Python objects based on immutable keys. But CherryPy might be easier. Good luck. Stuart On Thu, 2006-10-12 at 22:40 -0700, Sanjay wrote: > > http://www.danga.com/memcached/ > > Thanks a lot. > > Browsing some documentations yesterday, I came across caching fliters > in CherryPy. Any idea how it compares to memcached? I get the initial > feeling that caching filters would be more easy, flexible and powerful > compared to memcached. But this is just a feel, and might be far from > reality. > > sanjay > > > > > -- Stuart Clarke <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
