Hi Ben, On 3/16/06, Ben Bangert <[EMAIL PROTECTED]> wrote: > So that, combined with some session and caching middleware: > http://beaker.groovie.org/
Is beaker just sessions or does it (will it?) also do caching? > Gets us to a fairly powerful functional equivilant to CherryPy in a > bunch of different ways. There's now a fairly easy to use way of > registering objects with module globals in a way that "safe" for WSGI > embedded usage. There's a starting point for a more generic WSGI > request object, and there's some additional session middleware if the > paste and flup session middleware isn't good enough. > > CherryPy has done TurboGears a lot of good, and its increasing > WSGI-ness definitely helps, especially since those using filters are > somewhat reliant on its features. For First-class, these parts > definitely would help make for a powerful TurboGears base, one that > allows incredible flexibility. CherryPy has done TurboGears a lot of good. I still think it's a great (and fun!) way to develop apps. I don't think there's much filter usage among TG users, because TurboGears itself includes many of the features people use filters for. So, there is some implementation flexibility for First Class. > Anyways, some thoughts for those interested in future TG directions. :) Thanks! Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
