pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Roberto Mello <rmello@cc.usu.edu>
To: Christian Marschalek <cm@chello.at>
Cc: 'Andrew Hammond' <drew@waugh.econ.queensu.ca>
Cc: [PHP] PostgreSQL <pgsql-php@postgresql.org>
Subject: Re: HTTP authentication
Date: Sat, 28 Apr 2001 09:17:25 -0600
Message-ID: <20010428091725.A19929@cc.usu.edu> (raw)
In-Reply-To: <000201c0cf5c$3e9a14c0$0200a8c0@server>
References: <20010427142113.A22847@waugh.econ.queensu.ca>
	<000201c0cf5c$3e9a14c0$0200a8c0@server>

On Fri, Apr 27, 2001 at 10:54:21PM +0200, Christian Marschalek wrote:

> > Otherwise, you can reasonably use 
> > either the http auth stuff, which is probably the best approach, 
> > especially for a site that's got any kind of heavy usage or 
> > something based on PHP sessions.  However be forewarned that 
> > the sessions stuff isn't exactly the most efficient and fast.

	What's the problem with sessions? Are they slow? I don't see why since
it just grabs the cookie  from the browser and reads the appropriate file
from the sessions directory.
 
> Well PHP auth and sessions is probably the right aproach. Which one
> would be more efficient or faster?

	I just wrote an auth library that uses sessions and stores passwords
encrypted in the database. I am fairly new to PHP (tho experienced in
other web devel technologies) so it might need improvements, but it works
very well for me.

	-Roberto
-- 
+----| http://fslc.usu.edu USU Free Software & GNU/Linux Club |------+
  Roberto Mello - Computer Science, USU - http://www.brasileiro.net 
       http://www.sdl.usu.edu - Space Dynamics Lab, Developer    
let length(Long_Walk) > length(Short_Pier)



view thread (14+ messages)  latest in thread

Message-ID: <20010428091725.A19929@cc.usu.edu>
Permalink:  ../20010428091725.A19929@cc.usu.edu/
Also on:    postgresql.org/message-id/20010428091725.A19929@cc.usu.edu

 · 

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: rmello@cc.usu.edu, cm@chello.at, drew@waugh.econ.queensu.ca
  Subject: Re: HTTP authentication
  In-Reply-To: <20010428091725.A19929@cc.usu.edu>
  References: <20010427142113.A22847@waugh.econ.queensu.ca> <000201c0cf5c$3e9a14c0$0200a8c0@server> <20010428091725.A19929@cc.usu.edu>

* 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