On Wed, Dec 15, 2010 at 10:13 AM, Daniel Holth <dho...@gmail.com> wrote: > -1 I think the word 'resource' is at least as overloaded as the word > 'model'.
I'm tending toward -0. Best to leave the existing terminology until a more compelling name is found for traversal-model, one that is less ambiguous than "model" or "resource". Coming from Pylons, I wasn't bothered that much by the word "model" in Traversal. I just took it as "a different kind of model than my SQLAlchemy applications use" and left it at that. Maybe a beginner would have more trouble. But I think that can be worked around by defining "model" in both the traversal chapter and wherever models.py is introduced, and mentioning in both places that the two senses are not always identical. The problem is similar to HTTP sessions vs SQLAlchemy sessions, where people have settled on "session" vs "Session"/"dbsession". Pylons/Routes is already having a problem with the term "resource", which formally means an Atom-compatible resource (map.resource()), but users naturally use the other meanings as well. Adding another meaning to "resource" on top of those is problematic, especially if the term might change again later. How about that word "sitemap" you used in your original email. Or something-map. URL map? Object map? The words "map" and "mapper", while central to Routes, are less important for URL Dispatch, so perhaps we can cede those words to traversal. Because the URL Dispatch rules seem more like a list of rules than a map. The main thing is to keep the distinction between "business logic" and "view logic/framework logic". Even if MVC is passe, this distinction is still a good general guide, and models.py serves as a manifestation for business logic. So if you can say that traversal-model is based on this conceptually, then you can say that it sometimes manifests itself as something alongside models.py/"the business logic" rather than identical to it. -- Mike Orr <sluggos...@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.
