Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25251 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 57883 invoked by uid 1010); 8 Aug 2006 23:38:33 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 57868 invoked from network); 8 Aug 2006 23:38:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Aug 2006 23:38:33 -0000 X-PHP-List-Original-Sender: evert@filemobile.com X-Host-Fingerprint: 213.46.243.15 amsfep17-int.chello.nl Solaris 8 (1) Received: from ([213.46.243.15:2927] helo=amsfep14-int.chello.nl) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id F3/8F-13488-7CB19D44 for ; Tue, 08 Aug 2006 19:18:32 -0400 Received: from [192.168.123.105] (really [62.194.171.152]) by amsfep14-int.chello.nl (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20060808231828.DCTA13274.amsfep14-int.chello.nl@[192.168.123.105]>; Wed, 9 Aug 2006 01:18:28 +0200 Message-ID: <44D91BE0.3040303@filemobile.com> Date: Wed, 09 Aug 2006 01:18:56 +0200 User-Agent: Thunderbird 2.0a1 (Windows/20060724) MIME-Version: 1.0 To: steve CC: php internals References: <57792e850608081529g25f22a28wf768fcffe8801bb5@mail.gmail.com> In-Reply-To: <57792e850608081529g25f22a28wf768fcffe8801bb5@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Upload progress From: evert@filemobile.com (Evert Pot) Easiest way to go would then be flash or a java applet.. all the other methods i can think of are either php extensions or perl.. steve wrote: > We do a "web 2.0" type upload, and show a spinner. When the file is > large or the connection slow, people sometimes abort thinking that > there was a problem. I'd like to show a progress bar. Is this possible > yet? Which version? I can't use perl on these servers (PHP only), so > I'm SOL. I've used a patch before, but a client does not want to use a > hacked up PHP on production servers. >