On Dec 17, 5:57 pm, Mark Ramm <mark.mchristen...@gmail.com> wrote: > The main reason behind me asking Chris about this is that I can > imagine writing a simple explanation of the "traversal" model which > makes sense to a variety of TG, Zope, and even Django users. > > It would go something like this: > > Pyramid dispatch is based on a two phase system. > > The first phase is called Resource Location, and in it we use the URL > (Universal Resource Locator) to find a resource. This is done by > taking items from the path, and looking them up in a set of nested > dictionaries called the ResourceTree. You can think of this as > looking up files and directories in a file system. You just walk > down the path elements until you get a file. That becomes the > "resource" that we then publish. > > Which, naturally brings us to the second phase which we call "Resource > Publication" uses additional information about the request (request > method, etc) and the resource to lookup a view callable, and call it, > passing in the resource we just found.
Thanks Mark, that made a lot of sense. And I think I understand Traversal now too :) I didn't really have a strong opinion about this topic until now - most arguments for and against kinda went over my head. With that explanation I think Resource is a good choice. -- Cheers Anton -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@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.
