Unless you invent some special magic, you'd lose transactions, too, wouldn't you? Or is that built into the ODB engine? (I don't know exactly how this thing is built.) Under BFS (BeOS) and NTFS 5 (Windows 2000) you don't even have to store properties externally, as these file systems support file attributes. On NTFS 4 (NT 4.0 and earlier) you could store the metadata as separate streams inside each file; this is a barely documented, largely overlooked feature of NT that is rarely used, and is in fact there for Mac resource-fork compatibility. But it would certainly work. I think it's a good idea, if only because FTP and WebDAV (at least as far OS integration is concerned) suck. -- Alexander Staubo http://www.mop.no/~alex/ "`This must be Thursday,' said Arthur to himself, sinking low over his beer, `I never could get the hang of Thursdays.'" --Douglas Adams, _The Hitchhiker's Guide to the Galaxy_

-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Anthony Pfrunder Sent: 28. juni 1999 02:29 To: zope@zope.org Subject: [Zope] RFC: Multiple databases

[The following is also in the Collecter under features. I'm posting this as it relates to the above messages.]

My thoughts on extensions to Zope:

I'm <will be> working on constructing an additional Data.fs plugin (dropover FileStorage.py) which may be of use. The idea is to store stuff on the native filesystem and put properties etc in prop.x (ie the properties for file1.txt are in prop.file1.txt). The advantage of this is that it allows ppl to have a smb connection to a shared directory hence allowing them to more easily update the files. Of course, this means that you lose the ability to undo changes.

This database could be enhanced by allowing it to reconize Microsoft Office documents and store properties directly in the document itself. This means that the properties now travel with the document.

The second part of this proposal is to produce a Product which allows you to "mount" a database onto a subpath. This is very similiar to importing the database except that they are kept separate. These means that toplevel stuff goes into one Data.fs and the department Data.fs contains /Department/... stuff. This way, you can have a consistent style across various webservers just by running multiple copies of Zserver. In addition, you could make toplevel.fs read-only to protect it. This Product should be able to handle different filesystems (ie the current one, the above one and others)

Cheers,

Anthony Pfrunder

_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope

(For developer-specific issues, use the companion list, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )