Previously Tim Hicks wrote:
> Hi,
> 
> At the risk of pouring fuel on the "where does it hurt" fire, I'm 
> interested in working with plone.app.content.
> 
> My reason being that for my application, Archetypes appears to be a huge 
> drain on both disk and RAM resources - to the point that I'm frequently 
> seeing MemoryError exceptions on my memory-constrained web host.
> 
> My application is actually a CMFBibliographyAT folder containing about 
> 1500 bibliographic references.  (There are no PDFs or anything else in 
> there, just the references.)  When I export this folder in the ZODB 
> sense, the resulting file is about 24,000KB.  When I export this folder 
> to bibtex (which is a structured text representation for bibliographic 
> references), the resulting file is about 1,400KB.  This is very striking 
> to me.
> 
> Question 1: Am I right to blame AT here?

Try a pack to see how large your database really is. Extra indexing and
other work during the import will inflate the ZODB.

> Question 2: Is an implementation of the core CMFBib content types with 
> plone.app.content likely to be a big improvement in terms of disk, 
> memory, and speed of my (sluggish) zope instance?

Perhaps. Perhaps not. You'll have to benchmark :)

> Assuming the answer to those two questions is "yes"...
> 
> Question 3: Can anybody point me to some example code that use 
> plone.app.content to create, register, etc content types in a plone 
> site?  I mean, everything including getting the type to appear in plone 
> add menus and having working edit forms, etc.


oi.plum in the collective

> Question 4: What's the current status of plone.app.relations?  Martin 
> Aspeli suggested that relations was a potential missing link when using 
> p.a.c, but that plone.app.relations was nearly there: 
> <http://markmail.org/message/hq2znwcaek2ye6wi>.

Works fine. There's a package that implemenats an AT field using it with
the same API as the standard AT reference field: plonerelations.ATField.
That package is likely to be renamed since it's name is a bit, well,
off. That shouldn't stop you though.

Wichert.

-- 
Wichert Akkerman <[EMAIL PROTECTED]>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.

_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers

Reply via email to