Re: New Package: HTML_DB

From: Date: Wed, 23 Apr 2003 13:17:49 +0000
Subject: Re: New Package: HTML_DB
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-15381@lists.php.net to get a copy of this message
Hi
I didn't see the classes sources, only the demo sources. Could you put them online?
Here they are (not LGPLed yet), suggestions about location, names and such are appreciated. DB_FORM Source: http://www.bitcetera.com/en/project/pear/src/DB_Form.php.txt Location: /usr/share/pear/HTML/DB/DB_Form.php
Demo:     http://www.bitcetera.com/en/project/pear
Please note that the calendar script currently used is not GPL compatible and thus legal issues may arise. I've asked the author about changing the licence and I'm also thinking about replacing it by the calendar used on pear.php.net which seems to be real open source. DB_AUTH Source: http://www.bitcetera.com/en/project/pear/src/DB_Auth.php.txt Location: /usr/share/pear/HTML/DB/DB_Auth.php
Demo:     http://www.bitcetera.com/en/project/pear
DB_Auth is indeed concurring code as the Auth package does very much the same with many more features. However, the aim of DB_Auth is to make the most likely case (session authentication based on SQL data) as easy to implement as possible. A webpage formerly using Apache's HTTP Auth can migrate to DB_Auth at almost no expense. Just create a login page, edit the 'dbauth' config file and use .htaccess to define what's protected. (You can even exclude single files from authentication.) Unlike with Auth you DON'T HAVE TO PUT ANY CODE into your protected pages. Still, is this enough a reason to have DB_Auth PEARed? What do you think? DB_LIST Source: not available yet Location: /usr/share/pear/HTML/DB/DB_List.php
Demo:     not available yet
I'm currently working on this package. It'll be ready to evaluate soon. -sven

« previous php.pear.dev (#15381) next »