Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:40337 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 23226 invoked from network); 8 Sep 2008 11:06:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Sep 2008 11:06:57 -0000 Authentication-Results: pb1.pair.com smtp.mail=martin.jansen@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=martin.jansen@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.200.170 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: martin.jansen@gmail.com X-Host-Fingerprint: 209.85.200.170 wf-out-1314.google.com Received: from [209.85.200.170] ([209.85.200.170:58989] helo=wf-out-1314.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B3/BC-58883-C4705C84 for ; Mon, 08 Sep 2008 07:06:55 -0400 Received: by wf-out-1314.google.com with SMTP id 26so1578145wfd.26 for ; Mon, 08 Sep 2008 04:06:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=J5APP5f5TRigZ/hLiBcmIEp7e1yRpci6SD2rVWHZBGE=; b=oxAlFwuaL1+b/e//mob9UNKIclnZdlyZp9t/st2S8pjyqQ5Sgkp8aMTOPdadrZa58Q NYsXFAaa4hmQ6sXw2TZXRdp2y/cUY+2Sl0Ikq1dKoD+MRUa0s1MOE82xWqgylgNZudBb vT5NNSbDayZVA0WtBz456233XnFemeXlyYJAY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=gbKVRod+FsbrMScIcqYg98eHB4myAZDBb0Qyab40lUzD83kbY9lAGZHUDiSllFql/X WK/drOHDvC6XiqMTiWDFyKIBgMEt/CIgeSMKjxSZKeAZTU9tBnoSfHIQT1ZXwLpDK8sL 44SxS7Pvwx5ZlVEvfwv6axtVEkCttfXLaWSI0= Received: by 10.143.8.17 with SMTP id l17mr5190722wfi.106.1220872010340; Mon, 08 Sep 2008 04:06:50 -0700 (PDT) Received: by 10.142.14.11 with HTTP; Mon, 8 Sep 2008 04:06:50 -0700 (PDT) Message-ID: Date: Mon, 8 Sep 2008 13:06:50 +0200 Sender: martin.jansen@gmail.com To: "Arnaud Le Blanc" Cc: "php internals" In-Reply-To: <200809081218.02471.arnaud.lb@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200809081218.02471.arnaud.lb@gmail.com> X-Google-Sender-Auth: 5cc22766b4be96c5 Subject: Re: [PHP-DEV] [PATCH][HEAD] Upload progress in sessions From: martin@divbyzero.net ("Martin Jansen") On Mon, Sep 8, 2008 at 12:18 PM, Arnaud Le Blanc wrote: > The patch allows to store upload progress informations in session variables. > These informations can be retrieved by an other script while the upload is > still in progress, allowing to provide feedback to the user. > Implementing this in the sessions extension makes this feature available to > every one. > Using the session extension for this purpose also allows to use the different > storage backends available. > I have written a RFC/documentation here: > http://wiki.php.net/rfc/session_upload_progress Would it be possible to use something like $_SESSION['foo']['upload_progress_123'] instead of storing the information in the top-level session space? I can imagine there being frameworks and such that put their session stuff in some special container like $_SESSION['foo'] so that their session data does not interfere with the data of other components or the application that makes use of the framework. Martin