Travis Miller wrote:
we've been using mount points quite extensively on our zope server. basically we have ~30 plone sites running on one zope instance (and expect more).
Wow. Why? ;-)
object within it, but that would be 20/20 wouldn't it? B-) ...but, the point is that we solved this by creating a new zope instance with its regular Data.fs file, creating the plone site with the desired id (www) in the root of that db, and then mounting that new Data.fs file, back into the actual zope instance we were working with.
This sounds like the correct thing to do :-)
so it seems as if the 'mount-point' directive in the zodb_db config indicates where the object is to be placed in the database tree, but also indicates where to pull the object from in the mounted db.
Correct.
part of finding the object includes walking back up the db tree...(like acquisition?)
No idea what you mean by this.
obviously this is not a configuration for zeo, but the same seems to still apply when split across a zeo configuration.
What do you mean by this? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk