At the risk of mentioning "the other" products - I wanted to comment that Alfresco takes this approach.. storing content metadata in the DB and actual content in the file system. Because we make extensive use of Alfresco in some of our product offerings here, I've had plenty of opportunity to look under the hood at their code, and see how they've set things up in general. I'm not sure how much specifics I should go into right now though...

But since Alfresco 2.0 source code is released under the GPL, I see no real reason why one cannot look at their source for ideas on how this can be done.

-tim

On May 7, 2007, at 11:49 AM, Dominique Pfister wrote:

Hi Ian,

On 5/5/07, Ian Boston <[EMAIL PROTECTED]> wrote:
would Commons transaction work for this ?

http://jakarta.apache.org/commons/transaction/file/index.html

Im happy to look into the FileSystemBLOBStore.

Yes, that should work and this would certainly make a great
contribution! As far as I can see, these are the things that
complicate the matter:

- One has to someway associate the database transaction and the
 transaction in the file system in order to ensure consistency and
 commit either both or none.
- Right now,  FileSystemBLOBStore will use repository relative
 directories, either ${rep.home}/workspaces/${wsp.name}/blobs or
 ${rep.home}/version/blobs, which will not work in a clustered
 environment, unless those directories are mount points. In order to
 simplify the setup, those directories should be made configurable.

Again, I'd love to see some solution, that transactionally (!)
persists simple data in a database and blobs in a filesystem folder.

Dominique

Reply via email to