> My question with this is, should we take some of the WSGI stack and > environment setup out of the paster template, and move it into the > framework. If we do this, it should be done with a couple of > functions which setup the SQLAlchemy environment, and wrap your app in > all the "required" middleware, etc.
'premature optimization is the root of evil' I think this might be a good idea, we could wrap some of default settings as tg functions, and point user how to customize them if they want to do that. But it's really hard to decide what's need to be wrapped, and what's NOT need to be wrapped though. > > The reason I'm thinking about this is that one of the complaints I've > heard about Pylons is that it is difficult to upgrade from one version > to the next because so many template changes are required. It's the truth indeed :~ And we should concern if it's still easy to syncing with current pylons template if we change some paster template. -- Fred --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
