On Wed, Jul 14, 2010 at 3:31 PM, Guyren G Howe <[email protected]> wrote: > On Jul 14, 2010, at 15:14 , Mike Orr wrote: > >> Well, it's clearly a hybrid application because standard TurboGears >> apps do not have custom routes. I looked this up to confirm. >> http://www.turbogears.org/2.0/docs/main/RoutesIntegration.html >> TG uses the catcall "*url" route to send all requests to >> ``RootController.routes_placeholder()``, which then dispatches to the >> appropriate TG action. > > I don't read that as saying that custom routes are non-standard. But anyway.
It's not prohibited or discouraged, but it's not part of a typical TurboGears application either. The whole point of TurboGears is that it preselects a whole suite of optional software for you, and that it uses decorators heavily rather than routing. So adding custom routes goes against the TurboGears "style". I don't know how TG would recommend implementing a REST service; that would be a good question to ask them. "paster restcontroller" works because TG doesn't go out of its way to disable non-TG Pylons features, in case you need to use them for an advanced/specialized situation. -- 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.
