One thing that may not be obvious: we normally say that Routes chooses the controller and action but that's not quite true. Routes merely matches named variables we've called "controller" and "action". Pylons uses "controller" to find the controller, whose .__call__ method is a WSGI application. The base controller calls the action method and converts the Response to a WSGI response.
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. -- 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 -~----------~----~----~----~------~----~------~--~---
