On Sat, 2011-01-15 at 13:07 +0100, Alessandro Molina wrote: > On Sat, Jan 15, 2011 at 9:42 AM, Alice Bevan–McGregor > <al...@gothcandy.com> wrote: > > On 2011-01-14 22:53:03 -0800, Rob Miller said: > > > >> Object dispatch is a TurboGears concept, not Pylons. > > > > I've retrofitted it to almost every web framework I've ever used from WebPy > > and CherryPy through to Pylons. Routes are an inherently limiting thing to > > me (one app I worked on actually exceeded the ~55KiB limit on regular > > expressions!) and I think the Pyramid folks generally agree with me. ;) > > > > Have to say that I also prefer object dispatch to any other > dispatching method. I'm really new to pyramid, so I might be wrong, > but probably something like that can be quickly achieved by > implementing your Controller base class on Pyramid overridding the > __getitem__ method to use for example Crank. > > The main difference that I see between object dispatch and traversal > is that object dispatch requires an additional functionality to > specify what you want to expose of your class and what you don't (like > a decorator), while both traversal and url dispatch do not have this > requirement as nothing is exposed until you explicitly declare it > should. >
The main thing that object dispatch and traversal have in common is that both involve a tree. Otherwise, they're not very similar. In object dispatch, the tree is the "view" code. In traversal, the tree is essentially data that can be viewed (and often mutated) by view code that lives elsewhere. - C -- 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.
