[prev in list] [next in list] [prev in thread] [next in thread] 

List:       zope3-users
Subject:    [Zope3-Users] multiple catalogs
From:       "Maken Seteva" <crapkonto () gmail ! com>
Date:       2007-08-19 22:58:52
Message-ID: 11146e980708191558h28828708t48cc9bcdb5e3dcd8 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi!I'm slowly getting more into Zope3 and now I'm trying to implement
multiple catalogs spread across several containers. My use case
(simplified): I have a bunch of Network instances (containers) which contain
potentially a lot of content objects.
I don't like the idea of having one huge catalog to query since you are not
interested in searching globally,only within one Network.

Would it make sense to make each Network instance a local site and register
a catalog in this site?
Or perhaps skip making the Network a site and just put the catalog in an
attribute Network.catalog, maybe less overhead but a problem with this
solution is you'd have to do some parent-traversal to find the site manager,
right?

Any opinions on these solutions, or perhaps a totally different idea?

If the site idea is prefered, would that impose any difficulties of having a
site in the root folder that handles the intids, since the content objects
can be moved between networks I'd want the intids to be handled globally.

Thanks for your time

[Attachment #5 (text/html)]

Hi!<div>I&#39;m slowly getting more into Zope3 and now I&#39;m trying to implement \
multiple catalogs spread across several containers.&nbsp;My use case (simplified): I \
have a bunch of Network instances (containers) which contain potentially a lot of \
content objects. <div><br class="khtml-block-placeholder"></div><div>I don&#39;t like \
the idea of having one huge catalog to query since you are not interested in \
searching globally,only within one Network.&nbsp;</div><div><br \
class="khtml-block-placeholder"> </div><div>Would it make sense to make each Network \
instance a local site and register a catalog in this site?</div><div>Or perhaps skip \
making the Network a site and just put the catalog in an attribute Network.catalog, \
maybe less overhead but a problem with this solution is you&#39;d have to do some \
parent-traversal to find the site manager, right? </div><div><br \
class="khtml-block-placeholder"></div><div>Any opinions on these solutions, or \
perhaps a totally different idea?&nbsp;</div><div><br \
class="khtml-block-placeholder"></div><div>If the site idea is prefered, would that \
impose any difficulties of having a site in the root folder that handles the intids, \
since the content objects can be moved between networks I&#39;d want the intids to be \
handled globally. </div><div><br class="khtml-block-placeholder"></div><div>Thanks \
for your time</div></div>



_______________________________________________
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users


[prev in list] [next in list] [prev in thread] [next in thread]