Some time ago I have modified ExtFile to allow for 3) as well. And now I've even published it ;-). <http://www.zope.org/Members/shh/ExtFile/> HTH, Stefan --On Montag, 07. April 2003 15:10 +0200 Oliver Bleutgen <myzope@gmx.net> wrote:
Thanks for the answer, and sorry for not being clearer, but I not quite sure myself how to really accomplish what I want. What I need is:
1) Files shouldn't be stored in the zodb 2) Files should be managable (delete, create, update) from zope 3) Files shouldn't be served from zope 4) No additional administration outside apache is needed.
The products I mentioned accomplish 1), 2) and 4). They can accomplish 3), but only if users always remember to link to these files in a "special" way, i.e. with a different path than they would link them if they were normal zope objects. FS Cache Manager accomplishes 3) (at least well enough for me), but not 4), while I wouldn't mind 2 lines in httpd.conf. That's why I thought about a product like LocalsFS which would just - instead of delivering the file when it's called from the web - raise a redirect to an appropriate URI where then apache would serve the file.
-- Those who write software only for pay should go hurt some other field. /Erik Naggum/