TG2 will use one default route that sends all traffic to your root controller's "route" method, which does object dispatch from there.
There's no reason you can't set up additional routes, actions and controllers that live alongside the TG style object dispatch. So those who prefer the routes method will be able to use it. TG2 will also provide a lookup function which works like default, but which can send you to a new object where you can continue dispatch. This makes creating restful resources a lot easier because you can do things like look up a username in the database in lookup. Unfortunately due to the fact that tg2 is under heavy development, this is only documented in the docstrings -- but those are much more extensive than you might expect. :) --Mark On 7/17/07, iain duncan <[EMAIL PROTECTED]> wrote: > > > On Tue, 2007-17-07 at 22:25 -0400, Mark Ramm wrote: > > TG2 will be more like TG1.1 than it is like pylons, in that we'll be > > keeping object dispatch, the basic controller API, and Genshi, and > > those are not standard in pylons. > > Thanks Mark, does that mean TG2 will not be using Routes? Anyone have > opinions on Routes vs CP dispatch for restful controller routing? > > Thanks > Iain > > > > > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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?hl=en -~----------~----~----~----~------~----~------~--~---
