LiveUser

Hi, ok Markus will soon recommit LiveUser to Perm_LiveUser. Anyways there are still some todo's left before LiveUser is really the mother of all ... :-) Anyways here is a list (sure there are things missing): - check flag if rights stored in session need to be reloaded (current plan is to touch a file for each active session that belongs to a user who's rights have changed) - create a package.xml - make liveuser capable to be run in different modes (simple, medium, complex) where different features are enabled to make the API simple and to remove possible performance eating features if they are no needed - fix broken backends This is a copy of the list on http://projects.21st-hq.de/liveuser/ (in the about section): Here´s the short-term TODO list: - Separate user information retrieval and ACL retrieval into different backend classes, allowing to have ACL information in a different data container as the user information (thanks to Kristian Koehntopp for this idea). - Add more API functions for writing ACL and user information (currently, only information retrieval is implemented as I always had a nice admin GUI for editing data which might not be enough for some people). - Fix the "remember me" feature (user login by cookie - potential security hazard but often requested). - Add "applications" on top of "authareas" to the ACL hierarchy. This will prevent autharea nameclashes between applications and makes the system even more flexible (thanks to Björn Schotte for the idea). - Add a unique user identifier besides the database´s primary key "user_id" which is not necessarily present when using an LDAP or SOAP backend (again, thanks to Björn Schotte for the idea). - Make an official release (haven´t made a final decision on the license yet. Will most likely be LGPL, PHP License or QPL). I´m open for suggestions as I don´t know much about the pro´s and con´s of each license yet. (Lukas sais: license is LGPL from all I know) And after that: - Add a SOAP backend class (Lukas sais: LDAP is also big on the list) - Make table names freely definable (Lukas sais: I don’t think this is a good feature, I have prefixed all tables with "liveuser_" in the MDB backend and this should suffice imho) - Add the possibility to use PEAR::Cache for the XML configuration file so it doesn´t have to be parsed again on each request - Clean up the code (it is about 90% compatible with PEAR coding standards already, but some things can be done more elegantly) (Lukas sais: I have cleaned up a lot of remaining issues, but PEAR Error handling still remains) - Write more example scripts covering the new API functions - Rewrite the admin GUI for easier integration in other applications and localization. - Write a tutorial I think that Markus wouldn’t mind if anyone would take up some of these jobs. Someothers he might really do himself. Dunno :-) If anyone wants to help please tell us what would interest you so that we can coordinate this rather large list of todo's. Regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Reuchlinstr. 10-11 Gebäude 4 1.OG Raum 6 (4.1.6) 10553 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de