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 Mon, 13 Dec 2004 13:22:52 -0800 (GMT-08:00), Bruce Douglas
<[EMAIL PROTECTED]> wrote:
> you might also look into 'bit torrent'...
You must have missed the part about 'cannot have this file in a
"public" location'.
>Just thought I would pick the collective brain on this one. I have
>a r
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
On Tuesday 14 December 2004 15:53, Richard Davey wrote:
> 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 re
Richard Davey wrote:
>So I came up with an idea that I'd like your opinions on: I built a
>small but friendly Windows application (<50KB in size) that will
>connect to the web server via HTTPS, check the download credentials
>and if all is ok, it then downloads the file via HTTP in
[...snip...]
> RL> always see when you install software.
>
> That would lock us into a platform specific environment too :) You
> don't run an Install Shield web delivery system by executing the setup
> file on a Mac just because you're at work and can burn it to CD :) I
> was more interested in c
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
hi..
you might also look into 'bit torrent'...
peace..
-Original Message-
From: Richard Davey <[EMAIL PROTECTED]>
Sent: Dec 13, 2004 11:53 AM
To: [EMAIL PROTECTED]
Subject: [PHP] Delivering large files via PHP (>300MB)
Hi all,
Just thought I would pick the colle
Hi all,
Just thought I would pick the collective brain on this one. I have
a requirement to deliver a large EXE file to customers after they
order. The file is just under 400 MB in size and, because they have
just purchased it, I obviously cannot have this file in a "public"
locatio
12 matches
Mail list logo
