Hello rouvas,
Tuesday, December 14, 2004, 2:45:16 PM, you wrote:
r> Not to the web root, but to an arbitrary named on-the-fly created dir
r> protected with a *custom* (and different for each dir) .htaccess file (and
r> accompanying htpasswd entries). Then, there would be no single pass to share.
On Dec 14, 2004, at 8:53 AM, Richard Davey wrote:
Tuesday, December 14, 2004, 1:33:07 PM, you wrote:
r> Why don't you take the PHP out of the loop entirely?
r> Make a dir into the Apache area with a custom .htaccess
r> (with usernames/passwords, etc) and put the required files there.
Then the files
Hello Bruce,
Monday, December 13, 2004, 9:22:52 PM, you wrote:
BD> you might also look into 'bit torrent'...
Not really any use at all in this situation.
Best regards,
Richard Davey
--
http://www.launchcode.co.uk - PHP Development Services
"I am not young enough to know everything." - Oscar
Hello rouvas,
Tuesday, December 14, 2004, 1:33:07 PM, you wrote:
r> Why don't you take the PHP out of the loop entirely?
r> Make a dir into the Apache area with a custom .htaccess
r> (with usernames/passwords, etc) and put the required files there.
Then the files have to be within the web root a
Hello Greg,
Monday, December 13, 2004, 9:42:30 PM, you wrote:
GD> Use set_time_limit(0); to prevent the timeout. ignore_user_abort() is
GD> pretty handy too.
Yeah, I have the time-out limit in there already (the client end will
detect for a time-out from the server as well).
GD> If that doesn'
Hello Richard,
Tuesday, December 14, 2004, 12:02:19 AM, you wrote:
RL> This sounds an awful lot like various web installers.
Sure, there's nothing unique about the concept. The aim was to reduce
to load on the web server and make things a little easier for the end
user. You can code Install Shie
6 matches
Mail list logo
