Bug #2632

Container for LiveUser

Details

Request #2632	Container for LiveUser
Submitted	2004-10-27 14:57 UTC
From	leocsilva at dr dot ufu dot br
Status	No Feedback
Package	LiveUser
PHP Version	5.0.2
OS	Windos XP
Roadmaps	(Not assigned)

Comments

[2004-10-27 14:57 UTC] leocsilva at dr dot ufu dot br

Description:
------------
I made a translation of the container (Admin, Auth and Perm) for LiveUser PEAR::DB for ADODB. It would like to contribute with it.

[2004-10-27 15:17 UTC] smith at backendmedia dot com

Could you provide a link to the source?

[2004-10-27 16:12 UTC] leocsilva at dr dot ufu dot br

Link to the source of Container for ADODB

http://patolino.dr.ufu.br/~leocsilva/ADODB_Container/

[2004-10-27 16:45 UTC] smith at backendmedia dot com

Ok, we will see how we can incorporate it. We are actually planning a large overhaul of how we interact with the storage layer. You can see some more details here:
http://article.gmane.org/gmane.comp.php.pear.liveuser/2815

I am not sure yet, but maybe we can add your driver to the 0.14.x release. I do ask that you make it clear that you will support this set of drivers.

Finally you may want to add information about your driver on our wiki:
http://pear.limbourg.com

[2004-10-27 17:27 UTC] leocsilva at dr dot ufu dot br

I moved *.php for *.phps, and created one tar.gz. :)

[2004-10-27 17:54 UTC] leocsilva at dr dot ufu dot br

I really violated some rules of PEAR CS :).

Containers exhaustingly had still not been tested, to be sincere.

I decided to make this first contact with intention to perceive as it would be the acceptance and was very motivated to repair the archives.

Thanks.

[2004-11-23 16:19 UTC] smith at backendmedia dot com

If you are still interested, we have completed refactoring of the client and admin permission storage layer. You can find them in the LiveUser and LiveUser_Admin CVS directories. You will notice that it will be much less work this time around.

[2005-02-05 02:08 UTC] smith at backendmedia dot com

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.