On 11/12/2008, at 1:47 AM, Mark Ramm wrote:
> >> I'm very interested to hear about how TG2 will avoid the scaling and >> traffic issues that hit pownce and twitter. > > Well, there are lots of issues, and without being super-connected to > either Twitter or Pownce, one of the things that seems to have > happened to both early on is that it was difficult for their platform > of choice to connect to multiple databases and handle horizontal > partitioning. Various levels of caching are also important for scaling high traffic sites. Does TG2 offer any inbuilt object and/or template caching mechanism (using memcached or similar)? Or does it rely on Pylons/Beaker for caching? While learning some Django recently I was pleased to see that it offers caching support out of the box. Pylons offers caching with Beaker. I assume Beaker is also the recommended caching solution for TG2, but would like clarification. Cheers, Chris Miles --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
