On Thu, 2008-12-11 at 15:21 -0600, Jorge Vargas wrote: > > On Wed, Dec 10, 2008 at 11:44 PM, Chris Miles <[email protected]> wrote: > > > > > > On 11/12/2008, at 4:36 PM, Mark Ramm wrote: > > > >>> I assume Beaker is also the recommended caching solution for > >>> TG2, but would like clarification. > >> > >> Yes, beaker is the built in caching mechanism of TG2. Beaker supports > >> memcached, and lots of other back-ends. It also doesn't suffer from > >> the so-called dog-pile effect i the same way as some other > >> web-framework's built in caching mechanisms do, because it's just > >> plain awesome. > > > > That's good. I've decided to learn standard Pylons before looking at > > TG2 in detail. I assume a lot of Pylons knowledge will make working > > with TG2 much easier. > > > >From the experience of someone that did that, You will be disappointed > and you will learn a lot. From someone that comes from TG1 or django, > pylons is like giving you a 10000 pieces puzzle with no picture of the > image and a lot of ocean and sky tiles. So you have to expend a lot of > time reading about the components and understanding how things are > done, and ones your finally done with all those blue tiles you have no > energy to get started with the ship. And this is exactly the kind of > thing TG2 is here for. You start right there at the ship and if you > don't want to expend countless hours on the sky and sea, you don't > have to, but if some part of it is important you can dive in there.
OMG, that was hilarious Jorge. What a perfect metaphor. ;-) Iain --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
