Currently using routes in TG makes sense only for compatibility with Pylons controllers as you cannot map a TG controller to a route due to object dispatch getting in the middle trying to solve the route itself after routes already did it.
As routes is performed for each request is a performance bottleneck for no benefit in 99% of TG projects, so it is probably fine to disable it and require an enable_routes=True option in app_cfg to enable it again. It would require little effort for people that use it to get it back and it would avoid getting between people that don't use it speeding up the routing process by default. -- 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.
