[Zope-dev] Product Data Storage

[Monty Taylor]

Just my $0.02 worth... 

If you can at all avoid it, I think you should find a way to store it in 
the ZODB. 
Maybe a Configuration product that would allow you to create arbitrary 
configuration information and still be able to access it without making 
filesystem calls. Think about DC's Zope on a CD demo. Not that you really 
need to do that sort of thing, but it's really not going to work if you 
have to write stuff to the filesystem.

Actually, an XML Docment somewhere at root level should give you the kind 
of flexibility you're looking for. Lot's of people are using XML files 
for conf these days (they're all jumping... don't you want to...) 

That being said, I totally agree that if you need to store something in a 
file, put it in Zope/var. I, for one, have my Zope application code on 
partition along with other apps, and the data, like Data.fs on another. I 
typically don't expect the apps partition to grow very much, or very 
often, In fact, only when I install something. So it would be quite 
shocking to have that space filling unexpectedly.

But, as always, the choice is completely up to you.

Monty

>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

On 6/30/00, 3:27:42 PM, Dan "L." Pierson <dan@sol.control.com> wrote 
regarding [Zope-dev] Product Data Storage:


> Andy Dawkins writes:
>  > I have decided AGAINST searching the ZODB for instances of ZMailIn 
because
>  > that is just too scary, hideously inefficient and I don't want to go 
there.
>  > Instead I thought of keeping an up-to-date list of where all the current
>  > instances where held.  My original idea was to get the ZMailIn product 
to
>  > write a file in to the /lib/python/Products/ZMailIn directory, which
>  > shouldn't cause any problems that I can see.

> ... snip ...

>  > So my question is this:
>  > What are peoples opinions on storing shared product data?  Where should 
it
>  > be placed?  Should this ability be added to Zope as a standard?

> Shared data should go in zope/var, or a subdirectory of that.
> Zope/lib should be considered read-only by running products unless
> explicitly changed by the user.  As you have correctly pointed out,
> lots of machines share Zope installations for multiple servers.

> A standard interface for Python code to get a private subdirectory of
> var might well be useful.


> _______________________________________________
> Zope-Dev maillist  -  Zope-Dev@zope.org
> http://lists.zope.org/mailman/listinfo/zope-dev
> **  No cross posts or HTML encoding!  **
> (Related lists -
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope )