Mako uses beaker for caching so it should support any of those backends. There's a little bit of hardcoding to particular Beaker backends in 0.2.2 which is removed in the current trunk (also in prep for the new release of Beaker), but even with 0.2.2 that can be worked around by adding the desired Container class to mako.cache.clsmap.
On Jul 21, 4:46 pm, "Mike Orr" <[EMAIL PROTECTED]> wrote: > On Mon, Jul 21, 2008 at 12:52 PM, Michael Bayer <[EMAIL PROTECTED]> wrote: > > > is that test from the spitfire suite ? I haven't looked at it, but > > their Mako numbers look a whole lot like Myghty, not Mako (Mako is > > roughly the same speed as Cheetah in reality, a tad slower usually). > > > I haven't had the time to deal with spitfire, which will involve > > verifying that they are testing against Mako and not Myghty, and then > > spending the time to plug Psyco into Mako (should be a three liner) to > > see if that closes the gap (since they certainly aren't running pure > > python to get that kind of result). Can you perhaps tell me if that > > suite is in fact using mako and not myghty ? > > Mako is impressive because it approaches Cheetah's speed even though > Cheetah has a C extension and Mako doesn't. > > MikeB, would it be feasable to have an optional caching backend in Mao > that stored cached templates in Datastore rather than as files? > Beaker did something similar to save sessions in Datastore, since you > can't write files in App Engine. > > -- > Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
