I have a thought - <BR>don't do it. Why send files to a DB? Use filesystems to store <BR>files. A better thing to do would be to send the file to the<BR>hardrive and place a reference to it in the DB. For instance,<BR>say you allow users to upload mp3's and you want to be able to download them. You write the file to the server then place the<BR>path to that file in the DB.<BR><BR>Placing files in a DB places unnecessary strain on resources <BR>that could be eliminated by the solution above. Actually I've<BR>seen the above solution used by quite a few large sites. For <BR>instance - Nasdaq.com stores the path to their images in a DB.<BR>When a new ticker symbol is added they only need to replicate the<BR>file to a directory and place path reference in the DB. This<BR>takes the strain off the DB since it only returns a small string.<BR>
You know, I've often thought about that when Im out<BR>on my quest to build my app/music 'archive'. It could be useful.<BR>Especially if the server has better bandwidth then the<BR>client Im on, or if Im restricted to http only. I know<BR>that there are remote ftp clients but Im not sure If anyone<BR>has used them in a web app. I'd be interested in anything you <BR>come up with.