Direction of PEAR Auth

As the new maintainer of the Auth package I just wanted to
outline my
immediate direction for the package. My very first goal is
to get as
many bugs as possible fixed and get a stable 1.3.0 out there
for folks
to use.

To help in this if you have open bugs on the Auth package
could you
please check if they still exist in the latest release of
Auth and if so
mark them against that release in the bug tracker.

After a stable 1.3 is out I have no plans on where to take
the Auth
package. A number of people have suggested breaking the Auth
backends
into their own packages and this is one option I am
considering.

Adam Ashley

Adam Ashley wrote:

>As the new maintainer of the Auth package I just wanted
to outline my
>immediate direction for the package. My very first goal
is to get as
>many bugs as possible fixed and get a stable 1.3.0 out
there for folks
>to use.
>
>To help in this if you have open bugs on the Auth
package could you
>please check if they still exist in the latest release
of Auth and if so
>mark them against that release in the bug tracker.
>
>After a stable 1.3 is out I have no plans on where to
take the Auth
>package. A number of people have suggested breaking the
Auth backends
>into their own packages and this is one option I am
considering.
>
>Adam Ashley
>  
>
This isn't really a high priority or anything, but I think
it would be
nice to have a PDO Auth container.

-- Matthew

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

On Mon, 2006-02-20 at 20:16 +0000, Matthew Fonda wrote:
> This isn't really a high priority or anything, but I
think it would be
> nice to have a PDO Auth container.
> 

File a request on the bug tracker for this where someone can
contribute
some code . 

Looking through the bug tracker there are a couple of
contributed
backends (notably the kerberos backend) that I'll prob look
at including
in a 1.4.0 after we get a stable 1.3 out there

Adam

Matthew Fonda wrote:
> This isn't really a high priority or anything, but I
think it would be
> nice to have a PDO Auth container.

A generic Database container already exists based on
Pear:B.

Does it really worth to create for Auth another DB container
based on
PDO, as we know that a new PDO type is going to be added
into Pear:B ?

Regards,

Hugues

----
Hugues Peeters

phone  : 32 (0) 10 47 85 48
e-mail : hugues.peetersclaroline.net
web    : http://www.claroline.net
----

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Hugues Peeters wrote:

> A generic Database container already exists based on
Pear:B.
> 
> Does it really worth to create for Auth another DB
container based on
> PDO, as we know that a new PDO type is going to be
added into Pear:B ?

Directly using PDO should be noticelable faster.
Also I have not seen anyone work on a PDO based PEAR:B
driver.

regards,
Lukas

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Adam Ashley wrote:

>As the new maintainer of the Auth package I just wanted
to outline my
>immediate direction for the package. My very first goal
is to get as
>many bugs as possible fixed and get a stable 1.3.0 out
there for folks
>to use.
>
>To help in this if you have open bugs on the Auth
package could you
>please check if they still exist in the latest release
of Auth and if so
>mark them against that release in the bug tracker.
>
>After a stable 1.3 is out I have no plans on where to
take the Auth
>package. A number of people have suggested breaking the
Auth backends
>into their own packages and this is one option I am
considering.
>
>Adam Ashley
>  
>
I had some tests working with the last stable 1.2.4, HTTP
authentication 
not using Auth_HTTP but same.
1.3.0r3 was breaking them, 1.3.0RC6 looks OK.
cheers.
-- 
toggg
*
*

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Adam Ashley wrote:

>As the new maintainer of the Auth package I just wanted
to outline my
>immediate direction for the package. My very first goal
is to get as
>many bugs as possible fixed and get a stable 1.3.0 out
there for folks
>to use.
>
>To help in this if you have open bugs on the Auth
package could you
>please check if they still exist in the latest release
of Auth and if so
>mark them against that release in the bug tracker.
>
>After a stable 1.3 is out I have no plans on where to
take the Auth
>package. A number of people have suggested breaking the
Auth backends
>into their own packages and this is one option I am
considering.
>
>Adam Ashley
>  
>
I do some inquiries about bad uses of includes based on
__FILE__
Auth is there for this:
Auth/Frontend/Html.php:           
include(dirname(__FILE__).'/md5.js');

I don't think the __FILE__ is necessary there.
Possibly put it away.

Regards
-- 
toggg

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php