pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adam Witney <awitney@sghms.ac.uk>
To: pgsql-php <pgsql-php@postgresql.org>
Subject: Re: Transaction including two web page + timer
Date: Fri, 15 Nov 2002 09:40:56 +0000
Message-ID: <B9FA71A8.B89E%a.witney@sghms.ac.uk> (raw)
In-Reply-To: <Pine.BSF.4.44.0211100921090.92392-100000@themode.com>

On 10/11/02 2:29 pm, "brew@theMode.com" <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.




view thread (9+ messages)  latest in thread

Message-ID: <B9FA71A8.B89E%a.witney@sghms.ac.uk>
Permalink:  ../B9FA71A8.B89E%25a.witney@sghms.ac.uk/
Also on:    postgresql.org/message-id/B9FA71A8.B89E%a.witney@sghms.ac.uk

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: awitney@sghms.ac.uk
  Subject: Re: Transaction including two web page + timer
  In-Reply-To: <B9FA71A8.B89E%a.witney@sghms.ac.uk>
  References: <Pine.BSF.4.44.0211100921090.92392-100000@themode.com> <B9FA71A8.B89E%a.witney@sghms.ac.uk>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox