-1 I think the word 'resource' is at least as overloaded as the word 'model'.
If it's a graph it could contain nodes? After an "aha" moment, I always thought of my bfg app as having a traversal model /and/ a data model, with the leaves of the traversal model tending to be SQLAlchemy mapped classes with an __acl__ added by the traversal model. I think about my application as having two kinds of models. The traversal model defines the URL structure and provides subsets of the data model depending on the path. The data model includes the SQLAlchemy mapped classes and at some point the actual tables in the database. Originally I was afraid I would have to do a lot of work to make my database look like the ZODB, but that turned out not to be the case. Most of the complex SQL queries did wind up in the traversal model. Daniel -- 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.
