[Zope-dev] Warning! TransparentFolders and ZClasses

[Kevin Dangoor]

----- Original Message -----
From: "Phillip J. Eby" <pje@telecommunity.com>
To: "Jason Spisak" <444@hiretechs.com>
Cc: <zope-dev@zope.org>
Sent: Thursday, May 04, 2000 3:12 PM
Subject: Re: [Zope-dev] Warning! TransparentFolders and ZClasses


> At 06:57 PM 5/4/00 +0000, Jason Spisak wrote:
> >Well I have a folder called Candidates which contains 15,000 candidates,
> >and each candidate contains a resume.  Isn't that 30,000 objects in the
> >Candidates namespace?
>
> I would suggest you move them to a Rack/Specialist combination, which is
> designed for this sort of thing.  You'll still have the data in the ZODB,
> but it won't be as attributes and you'll avoid the boatloads of memory
> issue.  Plus, you won't have the enormous disk space hits that occur
> whenever you add another candidate to the folder.  :)

How does the Rack alleviate this problem? As I understand it, an
ObjectManager has its contents as attributes... so when the object is
activated, you need to bring in the whole object. I'm just wondering how the
Rack works around this (and if there are still upper bounds to be
considering...)

Thanks,

Kevin