> This means you can substitute a TG 2 controller or any other WSGI > application instead of a Pylons controller. TG 2 does not have an > "action" method; instead it parses the remaining URL to find an > @expose'd method. TG's base controller then converts the return dict > to a WSGI response, and then you're back in Pylons again.
Exactly. We want to make Pylons integration a snap, but to keep the TurboGears distinctives: Object Dispatch Returning a dict @expose() decorators indicate which template/engine to use to render the response @expose() decorators can be stacked to implement content-negotiation One thing that I would add is that TG2 will ultimately add things like WSGI middleware which automatically wraps controller actions in transactions like tg1. Though this will be more flexibly configurable than it was in TG1. We'll also handle forms differently (using ToscaWidgets by default). --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
