[Phplib-users] What is the 'standard phplib install'?

[Giancarlo P. <gia...@na...>]

Phplib and programmers

I don't agree with Richard when he says that Phplib is a tool for
programmers, and though it shouldn't be a problem for them to twickle
with classnames and extensions.
My opinion is that programmers prefer to concentrate on their
specific application, be it a bugtracking system or a POP3 client.
Phplib core features seldom are programmers' main focus, they are tools.

Yes, Phplib is for programmers, but the problem they have to solve is
usually another, and most of them need a standard solution they can
engineer with
a minimum of effort, and that can be  integrate maybe by someone else
into sites they don't control. 
Most  want to have a readily usable Auth/User/Perm framework that lets
them handle the prompting of a login form as they like, and that
postpones the problem of site  integration into the hands of the site
admimistrator whom we can not suppose being an expert in
Phblib neither, nor interested in becoming one.


The admin eventually, by just following some coherent instructions and
without need to hack into the programmer's code, should be able to
adjust the site authentication tables with the insertion of the
necessary groups/perms to work with that app.

For this I think that a 'configurator' script and a declared 'standard
install'  can be the first choice for really a lot of people. 
My indagations say that it would interest far more than 50% of people
that implement Phplib user/auth features.

BTW what can be defined the 'standard Phplib install' with regards to
the core Auth/perm/USer features? What do most people implement? Auth
without Persistent User? Custom auth_preauth method?
Nobody/Default_User? MD5 passwds, crc login?