Hi all,
Emiliano Heyns wrote:
> - Blob serving. Generic attachments would be nice, but Midgard
> should at least make images, sounds, etc. first-class citizens and
> as such make them manageable by the admin interface and have the
> upcoming access control regulate them. What I would want to see
> is that if you install Midgard you would have no need for shell
> and/or ftp access for your content managers at all.
Just had an idea on this, we'll store the attachments in a table that
contains the metadata about the file and an url that points to the
actual data. The url could be a pointer to a file in the filesystem
(file:/etc/passwd !) or to a BLOB record in a separate blob table
(x-midgard-blob://Xhd0y2nFP+sFdn1rl3Nf). In fact it could even be a
generic http, ftp or other redirection.
There will be a function that writes the data to an output stream. The
Midgard library provides handlers for streaming file and blob data and
other handlers could be provided by other components (like http by
mod_midgard). There will be a similar function that stores data coming
from an input stream to a file or to a blob record.
This way the exact data storage method can be flexibly determined
according to the requirements of the host system. When the sites are
packaged, all attachments are mapped to blob records and stored as such.
When the package is uploaded to another database, then the local
configuration determines whether the attachments end up being stored as
files or as blobs.
There will be no access control records for the blob table as the blob's
cannot be directly accessed (there will be no mgd_get_blob() function).
Instead the data access is controlled via the attachment records that
contain the link to the actual data.
Jukka
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
