Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26088
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 204.11.219.139 cause and error)
Message-ID: <453686A1.3050906@lerdorf.com>
Date: Wed, 18 Oct 2006 12:55:13 -0700
User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909)
MIME-Version: 1.0
To: Michael B Allen <mba2000@ioplex.com>
CC: fred@fmoses.com, internals@lists.php.net
References: <9A.94.57502.9A656354@pb1.pair.com>	<453656FE.8020602@lerdorf.com>	<20061018153630.0d1339c3.mba2000@ioplex.com>	<453682D4.4010200@lerdorf.com> <20061018155025.4ccca82e.mba2000@ioplex.com>
In-Reply-To: <20061018155025.4ccca82e.mba2000@ioplex.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Upload progress
From: rasmus@lerdorf.com (Rasmus Lerdorf)

Michael B Allen wrote:
> On Wed, 18 Oct 2006 12:39:00 -0700
> Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
> 
>> Michael B Allen wrote:
>>> On Wed, 18 Oct 2006 09:31:58 -0700
>>> Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
>>>
>>>> Fred Moses wrote:
>>>>> What ever became of support for a progress bar during file upload?  It 
>>>>> seems to have been relegated to the doldrums.  It would be extremely 
>>>>> handy for a commercial client of mine whose customers upload large image 
>>>>> files.
>>>> It's in 5.2.  You can see it running here:
>>>>
>>>> http://progphp.com/progress.php
>>> This is cool! How big can the files be? Are they limited to post_max_size
>>> and similar?
>> Yes, it's just the regular file upload code, so the same restrictions 
>> are enforced.
> 
> Can an extension get access to the client socket such that it can decode
> chunked POSTs of unlimited size?
> 
> I want to read buffers within the extension as opposed to writing it to
> a file.

You don't get to read it from the extension, but you do get access to 
the data in the just read buffer each time the hook is called.  Have a 
look at the rfc1867.c source code.  It's pretty straightforward.

-Rasmus