Hello, On Wed, Dec 15, 2010 at 8:13 PM, Chris McDonough <chr...@plope.com> wrote: > I'm considering making a fairly major terminology change to the Pyramid > docs. I'd like to consider renaming the term "model" to "resource" in > the docs.
I think "resource" term isn't suitable for this kind of thing, as being pointed already resource it's more like static resource (imgs, js, css, uploaded date). How about term "location"? I think it's more suitable: 1) In current terms model should implement ILocation interface, so it's location already and this is the only requirement that object should satisfy to take part in graph traversal, isn't it? 2) If we rename "models" to "locations" the process of context finding would have meaning of mapping from web locations (URIs) to application domain's locations. 3) Scala web framework Lift (the most popular Scala web framework) also has the notion of location and while it's not implemented with traversal but rather with mapping by user-specified function that make URL rewriting, I think term location is more suitable here — we can construct sitemaps, breadcumbs from location graph, also location sensitive permission model is more suitable for web apps, because views rare work with just one model at time. 4) Existence of repoze.bfg.traversalwrapper and repoze.bfg.traversaladapter (which are provides good patterns I think) also has no relation nor to resource, nor to model, but can provide good examples as mapping from application locations to domain models. -- Andrey Popp phone: +7 911 740 24 91 e-mail: 8may...@gmail.com -- 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.
