Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id D0C67476CDC for ; Fri, 15 Nov 2002 04:42:34 -0500 (EST) Received: from mailhub2.sghms.ac.uk (firewall.sghms.ac.uk [194.82.50.2]) by postgresql.org (Postfix) with ESMTP id 0AE1E475E42 for ; Fri, 15 Nov 2002 04:41:22 -0500 (EST) Received: from [194.82.51.24] (helo=imail) by mailhub2.sghms.ac.uk with esmtp (Exim 4.05) id 18CcxS-0002gO-00 for pgsql-php@postgresql.org; Fri, 15 Nov 2002 09:40:14 +0000 Received: from [172.16.20.3] (mrc1-003.sghms.ac.uk [172.16.20.3]) by imail.sghms.ac.uk (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7 2002)) with ESMTPA id <0H5M00A8A2VX9W@imail.sghms.ac.uk> for pgsql-php@postgresql.org; Fri, 15 Nov 2002 09:40:45 +0000 (GMT) Date: Fri, 15 Nov 2002 09:40:56 +0000 From: Adam Witney In-reply-to: To: pgsql-php Message-id: MIME-version: 1.0 User-Agent: Microsoft-Entourage/10.1.0.2006 Subject: Re: Transaction including two web page + timer Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT X-Spam-Status: No, hits=-103.5 required=5.7 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, SPAM_PHRASE_00_01,TO_LOCALPART_EQ_REAL,USER_AGENT, USER_AGENT_ENTOURAGE,USER_IN_WHITELIST version=2.43 X-Spam-Level: X-MailScanner: Found to be clean X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200211/69 X-Sequence-Number: 1651 On 10/11/02 2:29 pm, "brew@theMode.com" 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. > > Look into session variables, they are stored on the web server and > available to all the following instances of PHP scripts from each > particular user. It is set up with one line of code at the top of each > script and then you can pass the variables onto the following scripts, no > need to worry about the the details of file or database calls for the > temporary info, it's built into PHP. I am new to PHP, but I am trying to set up a system where a user logs in on one page and then does various database activities on subsequent pages. Each user will have their own username and password on the database. If I was to store the username and password as session variables... Is this generally considered a good idea... Or is it a security risk? Thanks for any advice adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.