On Jul 29, 2009, at 3:05 PM, Sean Thayne wrote:
It can be a shared resource, it can handle requests on the localhost
or by
vmware images in the same way.
I don't have to create a bunch of symlinks to folders and use nfs/
samba for
vmware images
It is password protected
I can easily attach additional information to a file, without actually
touching the file
I can use foreign keys to handle garbage collection of files
I can easily manage additional versions of files... For instance I
could
cache different versions of a image.
All in all I think it would just be much easier to manage a large
set of
files in a database, rather than a filesystem
Are you going to be (or planning to in the future) any sort of
database replication? I haven't tested this particular case, but I'd
expect the single threaded/serialized nature of MySQL replication have
some fits with 20MB data fields.
--
Joseph Scott
[email protected]
http://josephscott.org/
_______________________________________________
UPHPU mailing list
[email protected]
http://uphpu.org/mailman/listinfo/uphpu
IRC: #uphpu on irc.freenode.net