On 2011-3-17 15:59, Dylan Jay wrote:
So I think it's compelling to describe traversal in the manual as an advanced routing feature and make it more clear exactly what scenarios traversal is good for and why it's a great solution for those. I don't think that means moving traversal to the back because its too important.
I don't agree with that. Traversal is not 'advance' or 'more difficult'. It just approaches the URL->data+code mapping problem in a way which works great when dealing with a hierarchical data structure. That is not handled very well (I'm even tempted to say 'badly') by routing approaches. As a test I explained it that way in a training session this week, and everybody seemed to get the distinction directly.
Wichert. -- Wichert Akkerman <wich...@wiggy.net> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
