nathan r. hruby wrote:

>  If y'all will put together some ideas I would be happy to include a base
>  chapter in the phplib docs.
>  
>  This might be something worth taking to the phplib list as well, not just
>  -dev, as you'll reach a wider audience who may have tackled these problems
>  before...
>  

Ok then, I'll go on with my solo.

<IDEAS for guidelines for phplib-based packages design/integration> 

In the 100% of the cases, that is when using session,
people who configure phplib only have to:
-give a name to their session, user, auth, perm class
-choose a database to hold this

those who use user,auth and perm (60% ?) also want to:
-decide if they want default authentication 
-decide if they want md5 or plain pasword
-decide if they want send the password challenge response or plain text 
-choose a 'permission scheme'

These all cover maybe 90% of the cases.

The remainig 10% certainly needs  user, auth and perm, but has some
particular need that enforces a completely different authentication
process (preauth), or two or more different permission schemes, or more
than one session, multiple databases, or other extravagancies for which
we can suppose he is already well armed.

To make this 90% of the people happy, and their life easier, why not 
implement some nice _PHPLIB_ defines to hold these settings, and have
the Example_session and the rest go and check it first? No obligation,
one can always do it the usual way if he likes

But then package developers can be interested in having their classes,
too, go and check these defined values first, and if they're there adopt
them. Their packages would install and configure better, and they'd be
happy and buy a nice yacht.

Plain easy, plain simple, you (phplib developers) can invent as many
defines as you like, their use would remain facultative anyway.
Well, there's also some responsability, as from that moment on, you
become the 'registry' of these defines, and so you must take care not to
change them, drop or do other 'bad things' that people don't like.
Limit them to the minimum, which covers already the 80-90% of the needs. 

I let the ball to you guys now. I cannot go as forward as to state what
and what not. 
This is just my idea.

Giancarlo

-- 
Abbestellen mit Mail an:   phplib-dev-unsubscribe@[...].de
Kommandoliste mit Mail an: phplib-dev-help@lists.netuse.de