Received: from fslc.ser.usu.edu (fslc.ser.usu.edu [129.123.28.122]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f3SFHT364236 for ; Sat, 28 Apr 2001 11:17:29 -0400 (EDT) (envelope-from rmello@fslc.usu.edu) Received: (from rmello@localhost) by fslc.ser.usu.edu (8.12.0.Beta5/8.12.0.Beta5/Debian 8.12.0-1) id f3SFHPtU019958; Sat, 28 Apr 2001 09:17:25 -0600 Date: Sat, 28 Apr 2001 09:17:25 -0600 From: Roberto Mello To: Christian Marschalek Cc: "'Andrew Hammond'" , "[PHP] PostgreSQL" Subject: Re: HTTP authentication Message-ID: <20010428091725.A19929@cc.usu.edu> References: <20010427142113.A22847@waugh.econ.queensu.ca> <000201c0cf5c$3e9a14c0$0200a8c0@server> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <000201c0cf5c$3e9a14c0$0200a8c0@server>; from cm@chello.at on Fri, Apr 27, 2001 at 10:54:21PM +0200 X-Archive-Number: 200104/49 X-Sequence-Number: 302 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)