Re: uploadprogress extension

Ilia Alshanetsky wrote:

On 28-Sep-06, at 11:57 AM, Christian Stocker wrote:

Hi I wrote a little uploadprogress extension based on the rfc1867 patch committed to PHP 5.2 Worthy an addition to PECL?

I'd say so, +1.

The tricky part here isn't really the extension part that catches the hooks, but the server-side storage tie-in. You already mentioned possible support for memcached, and I added support for shared memory storage to APC a while back. The question then becomes whether each storage extension gets their own rfc1867 hooks, or we have a single mega extension that knows how to talk to every storage mechanism? That is, would pecl/uploadprogress eventually speak memcached, mysql, oci8, pgsql, mssql, firebird, frontbase, informix, odbc, ingres, etc? That seems like a nightmare to me. But by the same token, having each of these extensions implement their own hooks which may not be compatible would also be a mess. I think we need a single way to trigger the upload, and we need a consistent dataset we store in the backend so these things will be interchangeable. Have a look at: http://cvs.php.net/viewvc.cgi/pecl/apc/apc_rfc1867.c?revision=HEAD&view=markup And http://progphp.com/progress.php http://progphp.com/progress.phps for a working implementation. Perhaps what we need is a combination. A single extension that catches the hooks, but then the actual datastore part is handled by the individual datastore extensions by exposing some known interface specifically for doing this? -Rasmus