On Thu, Apr 16, 2009 at 1:29 PM, Nitsan Bin-Nun <nitsan@xxxxxxxxxxxx> wrote: > Hi List, > > I have been thinking for a while about setting up my own rapidshare.comclone, > Few days back I went really serious with this and came up with some ideas. > > This is where I need your help, my partner and I have been thinking about > the > system that the website should run on. > We came to conclusion that we are going to write it in PHP. > > There are several issues that came up during the mind-storm: > First, how we can keep the files out of being published as direct links? > > My first idea was to host them one directory up from the http directory. > It seems good but how I would deliver the files to the users? > We are talking about unlimited file-size hosting so that means that we > will have to stream the files somehow... and they will be BIG (it's > defendant, > about 700MB~ each) > > We thought of letting users pay by SMS'es, whats your ideas about it? > > I'm generally looking after a "do" and "NOT do" list of creating a file > hoster ;) > If you have any general ideas / precautions that would definitely make my > partner and I happy :) With files of that size and the transfer speed of most broadband users, you will almost absolutely have to use a Flash/Java uploader app in order to ensure the files finish before server/browser timeout. As far as hiding them from being accessed directly, I think you're right--the file itself will have to be outside of your web root. I would probably use a middle system to grab a request from your page, verify that it did in fact come from your page (maybe with a time-sensitive hash value) and then retrieve the file's contents based on the validity of that hash value. Just a thought. -- // Todd -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
