[pLog-svn] r2177 - in plog/trunk: class/dao class/dao/userdata config

Oscar Renalias phunkphorce at gmail.com
Wed Jun 8 07:50:12 GMT 2005


A phpnuke backend would also be cool to have :) As I said, I'd like to
see somebody working on this as soon possible, so that we can see what
problems we might face and how we could overcome them... I already
said I will try to work on the phpbb2, but more opinions would be nice
:)

Oscar

On 6/7/05, Reto Hugi <plog at hugi.to> wrote:
> Oscar,
> 
> This is great news! Thanks for picking up this very interesting feature.
> I'll certainly have a look at it once in a while. I could use this
> feature to integrate properly into one maybe even two PostNuke base
> Portals. I'll get back to you when I'm ready to work on this though :)
> 
> reto
> 
> On 06.06.2005 23:37, oscar at devel.plogworld.net wrote:
> > let's keep breaking things... this time, one of the most interesting features of 1.1 (IMHO): pluggable
> > user-data backends. The current Users class is now nothing more than a proxy class for the real
> > user-data backend class that is doing the dirty job. By default we will create packages using
> > plog's own PlogUserDataProvider but users willing to integrate plog with other tools such as phpbb2,
> > ldap, mambo or kerberos will be able to easily switch by editing one configuration file.
> >
> > Before you ask, the fact that this requires editing one config file is intentional. This is not a
> > feature that 98% of the common users will need to mess around with so there's not much point in
> > spending too much time making it pretty.
> >
> > The idea behind this feature is that plog will be able to use external sources of user data, instead
> > of using its own database tables, dynamically (as opposed to synchronizing the user data every day,
> > hour or once in a while) Whenever a user is added/removed/updated in the host application, these
> > changes will be immediately seen by plog and viceversa.
> >
> > This feature does *not* include single login mechanisms or anything like that yet.
> >
> > At the code leve, user-data "providers" are classes that extend the BaseUserDataProvider base class and provide all the methods that the original Users class provided. Since all client classes of Users expect a certain interface, this change does not break anything anywhere in the code.
> >
> > Please keep in mind that this is a first approach, and a very rough one. Nobody has even started
> > working on additional providers so we don't know what difficulties we can find when creating new
> > ones... I am planning to take a look at phpbb2 because it should be easy :), but so far the current
> > plog user data backend is working just fine.
> >
> > Let me know if you have any questions...
> 
> _______________________________________________
> pLog-svn mailing list
> pLog-svn at devel.plogworld.net
> http://devel.plogworld.net/mailman/listinfo/plog-svn
>



More information about the pLog-svn mailing list