On Fri, 2008-11-14 at 12:26 -0600, Ken Kuhlman wrote: > > I'm struggling with the decision of whether I should backport > "use_wsgi_app"-type functionality to tg1.1b2, if I should hold off > until 1.5, or even if it's a mis-feature that shouldn't be backported > at all. > > As a memory refresher, "use_wsgi_app" is a TG 2.0 feature that is used > to return a WSGI application from an exposed controller, and the > ticket for backporting it to TG 1.x is #1951. Anyway, here's why I'm > struggling: > > (a) I'm not sure that use_wsgi_app's interface is right. I think it > would be better if it allowed the WSGI app to be used directly from a > controller. For example, instead of this: > class MyController(Controller): > @expose() > def some_controller(self, *args, **kwargs) > return use_wsgi_app(your_wsgi_app)
My two cents are that: - it would be great to have this in 1.1 - it's more important that the interface be right then for it to come out sooner - even though it would be great, it's not worth killing yourself over for 1.1 as CherrPy 2 is on the way to "legacy" thanks for listening to the peanut gallery! 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 -~----------~----~----~----~------~----~------~--~---
