Re: [nyphp-talk] Writing large files to client efficiently

2008-01-10 Thread Michael B Allen
On 1/10/08, John Campbell <[EMAIL PROTECTED]> wrote: > > In your experience, how much slower is fpassthru compared to serving > > static content? Is it twice as slow? > > Well, I just tested it and it doesn't appear to make much difference. > You have to fire up the php interpreter either way. I

Re: [nyphp-talk] Writing large files to client efficiently

2008-01-10 Thread John Campbell
> In your experience, how much slower is fpassthru compared to serving > static content? Is it twice as slow? Well, I just tested it and it doesn't appear to make much difference. You have to fire up the php interpreter either way. I am running PHP+APC, and I see 4.2 ms for both requests with th

Re: [nyphp-talk] Writing large files to client efficiently

2008-01-10 Thread Michael B Allen
On 1/10/08, John Campbell <[EMAIL PROTECTED]> wrote: > On Jan 10, 2008 1:49 PM, Michael B Allen <[EMAIL PROTECTED]> wrote: > > What is the most efficient way to write large files to the client? > > > > fpassthru? > > > > Mike > > Yes. Make sure you are not output buffering, and don't forget to cal

Re: [nyphp-talk] Writing large files to client efficiently

2008-01-10 Thread John Campbell
On Jan 10, 2008 1:49 PM, Michael B Allen <[EMAIL PROTECTED]> wrote: > What is the most efficient way to write large files to the client? > > fpassthru? > > Mike Yes. Make sure you are not output buffering, and don't forget to call session_write_close() before running fpassthru() if you are using

[nyphp-talk] Writing large files to client efficiently

2008-01-10 Thread Michael B Allen
What is the most efficient way to write large files to the client? I want to control download access to uploaded files (and dodge all the security issues associated with allowing access to uploaded files) so I can't just serve it as static content - it has to be under script control. fpassthru?