On Feb 11, 11:26 pm, "Mike Orr" <[EMAIL PROTECTED]> wrote: > Werkzeug returns "string/string" instead of controller and action > variables. I don't think we want to do this, because controller and > action have served us so well. I think those are two totally different approaches. The controller/ action thing is perfect for REST scenarios and the pylons like controller/action model. The idea of werkzeug's endpoints is that you have something that is comparable as endpoint (usually a string) which is used for building and will be converted into a callable in the dispatcher. A pretty common approach is using import paths there and import the object with that path (usually a function). This is more the django like dispatching approach. I personally would probably use Routes 2 for Rails/Pylons like controllers because it was designed for that.
Regards, Armin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
