On Jan 9, 2011, at 10:55 PM, Wikus van de Merwe wrote: > Jonathan, can you explain a bit more about how the new routes would work on > some examples? How would the mappings below (just /c/f/args) look like with > the new routes? > /_ah/xmpp/message/chat/ -> /comm/jabber > /new-article -> /post/create > /about -> /article/2010/07/11/welcome-to-my-world > /article/2010/11/02/new-world-order -> > /article?year=2010&month=11&day=02&title=new-world-order > /article/2010/11 -> /article?year=2010&month=11 > /author/smith -> /author?name=smith > /publisher/smith/update -> /publisher-update?name=smith
In general, transformations like this will have to use the existing regex mechanism. Are you actually using those transformations? If the path on the left is the incoming URI, I'm not making sense of the paths on the right; we need to convert a URI into /a/c/f... for routing purposes. > > > I'll be checking in a new feature in a day or two that allows you to define > > app-specific routers in the root routes.py. > > I thought the goal is per application routes control for better > modularity/portability of apps. If so, global route management should be > minial and limited to the mapping to applications only. I don't think any > local/per application rules should be there. What is the reason why in your > proposition e.g. controllers of the default app are specified in global > routes instead of having them in the local ones? It's an option only, for those who want to define system routing centrally.
