Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id B4DE2475AFA for ; Sat, 9 Nov 2002 16:30:25 -0500 (EST) Received: from wolff.to (unknown [66.93.197.35]) by postgresql.org (Postfix) with SMTP id EA119475ADD for ; Sat, 9 Nov 2002 16:30:24 -0500 (EST) Received: (qmail 22340 invoked by uid 500); 9 Nov 2002 21:40:18 -0000 Date: Sat, 9 Nov 2002 15:40:18 -0600 From: Bruno Wolff III To: Zhidian Du Cc: pgsql-php@postgresql.org Subject: Re: Transaction including two web page + timer Message-ID: <20021109214018.GA22305@wolff.to> Mail-Followup-To: Zhidian Du , pgsql-php@postgresql.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.25i X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200211/42 X-Sequence-Number: 1624 On Sat, Nov 09, 2002 at 14:03:50 -0700, Zhidian Du wrote: > > > Good idea. One problem is that HTML is a stateless protocol. How can I > let application to hold the whole contents of the first page and second > page? PHP provides for session tracking. Somehow you have to be tying the two web requests together. You could store the information from the first request as a file or in a table in the database that holds the page 1 requests temporarily.