My only concern is about the timing. 2.2 needs to maintain, as cleanly as possible, backwards compatibility. For 2.2, we could make it an option that defaults to leaving routes enabled, and 2.3+ change the option to False.
Ideally, people should be able to migrate a 2.0 app to 2.2 without changing their code at all. 2.3 and up, though, is a whole new ballgame. Working on that document right now, so hopefully things can move forward again from me. On Wed, Feb 29, 2012 at 12:52 PM, Christoph Zwerschke <[email protected]>wrote: > Am 29.02.2012 12:52, schrieb Alessandro Molina: > > 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. >> > > +1 > > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears Trunk" group. > To post to this group, send email to > turbogears-trunk@googlegroups.**com<[email protected]> > . > To unsubscribe from this group, send email to > turbogears-trunk+unsubscribe@**googlegroups.com<turbogears-trunk%[email protected]> > . > For more options, visit this group at http://groups.google.com/** > group/turbogears-trunk?hl=en<http://groups.google.com/group/turbogears-trunk?hl=en> > . > > -- Michael J. Pedersen My Online Resume: http://www.icelus.org/ -- Google+ http://plus.ly/pedersen Google Talk: [email protected] -- Twitter: pedersentg -- 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.
