MS SQL 2K
maybe just the videos as they may need editing, eg. the admin user uploads the raw file (as a whole), then, either a contributor or publisher logs in and downloads the file and edits (separates into say 6 pieces then re-uploads). Then on the viewing site the finished product(s) is then viewed through an IFRAME.
Sorry about being vague...
Mark Mandel wrote:
Carl -
What DB would you be using?
Is there any workflow associated with the documents (e.g. revisions etc)? or is it just storage to shoot out to the 'wider public'.
It really can depend on the application...
Mark
On Fri, 23 Jul 2004 16:07:34 +1000, Carl <[EMAIL PROTECTED]> wrote:
Just having some interesting conversations...
Use a directory structure or store it into the database?
Just want to get some input on what is better, safer, easier to code, and easier to manage (just thinking of the cost of getting more db space compared to disk space, as some of the videos are 4mb a piece and there is normally 25 per customer, and there can be up to 500 customers or more at any one time)?
We have PDF docs and videos that get embedded into pages (pdf directory sits below webRoot and video sits above webRoot), some say that having a directory structure is better, but others say put it all into the DB as this is more secure, but others say this is slower...
Can you give me some feedback..
Thanks :)
Carl
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
