Login | Register
My pages Projects Community openCollabNet

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Catacomb] PHP ...

Yes, we are going to store only resource content in a file system. 
Also I like the several blobs idea,

If we could use Apache filters/handlers to provide PHP or CGI thing, it's
the best way to go, I guess.

Sung Kim, http://www.cse.ucsc.edu 

-----Original Message-----
From: catacomb-admin@webdav.org [mailto:catacomb-admin@webdav.org] On Behalf
Of mhubb@okcareertech.org
Sent: Wednesday, May 28, 2003 5:43 AM
To: Chris Knight
Cc: catacomb@webdav.org
Subject: Re: [Catacomb] PHP ...

Quoting Chris Knight <Christopher.D.Knight@nasa.gov>:

> Currently in the stream_dbms branch, if you specify DavDBMSFileDir it
> will store data external to the database in a hash directory structure.
> Otherwise it stores data in the BLOBs as before.
> I would warn against providing the "like dav_fs" mechanism, as you run
> into issues with filesystem naming restrictions and performance overhead
> (as previously discussed). I believe we can support PHP as I think
> Apache allows for "pipelining" request handlers, I will investigate over
> the next week or two.

For clarification, the intent is still to store resource/collection data in
filesystem, but your statement above means that Catacomb will probably need
name and arrange those data files in a manner that prohibits/makes difficult
direct access to these files through traditional methods (a shell for
 Metadata will be still be stored in the DB.  Do I understand?

Matt Hubbard

PS - we are moving toward using Apache filters/handlers to force PHP files
parse when stored within a Catacomb repository.  Correct?

This mail sent through IMP: http://horde.org/imp/
Catacomb mailing list