I'll probably get shot for this, but a pure filesystem and MySQL implementation is better suited for PHP. If say, you wanted to store the image info in the ZODB, and the data elsewhere, then Zope is a good solution. Another nice thing about Zope you don't get with a language like PHP is much better managability of the presentation code. If that's important, then again, Zope is the way to go. -jim ----- Original Message ----- From: <gabecker@indiana.edu> To: <zope@zope.org> Sent: Tuesday, November 05, 2002 4:24 PM Subject: [Zope] advice needed
I am relatively new to Zope, but I plan to use it for an image database system that I need to make for scientific purposes. What I have in mind is to store the actual images externally in files (since there will be many and large files), and the info about the image (where collected, owner, codes etc etc) in a database like MySQL. Zope would form the interface.
My first question is what would be a suitable way to go from here: use LocalFS or ExtImage for storage of many files (think of 50,000 or so)? I will need to be able to differentiate between users: ie not every user should have access to all files.
Furthermore: if there are people that have already done something similar I would appreciate to learn from their experience. Through a web search I haven't been able to find such projects, at least not based on Zope.
All best, Gabriel
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )