On 24/08/2006, at 8:31 AM, Jacob Kaplan-Moss wrote:
> > This is probably not what you want to hear, but I'd *strongly* > recommend that you not store files in the database. Filesystems are > made for, well, storing files, and it's almost always bad design when > you stuff them into a relational database. There is actually a argument to storing files in the database. it makes for easier replication, and you can have other benefits like having more meta-data. especially when you need to do things like remove all crud.. "find" can take forever. > > Add to that the fact the DAV is a pretty complicated protocol, and I > think you see why only a few projects actually implement it. you might want to look for a apache module which does something like this (mod_dav_fs for example does what you want but in a file system.. ) http://www.atmarkit.co.jp/flinux/special/webdav03/webdav01a.html describes something similar to what you want by the looks of the pictures (but in japanese) > > That said, Googling "python webdav server" gives me http:// > sandbox.xerox.com/webdav/, which at first glance might be what you > want. Google's nice, isn't it? > > Jacob > -- Ian Holsman [EMAIL PROTECTED] http://personalinjuryfocus.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
