[OpenID] JanRain library licensing (was: Re: On OpenID 2.0)
Chris Messina
chris.messina at gmail.com
Fri May 4 18:33:22 UTC 2007
That's fair. I wonder though if it might be possible to abstract parts
to simply reduce the amount of redundant OpenID code in the wild. If
that's not possible, that's fine -- but my interest is in having
people have a consistent and optimal OpenID experience -- no matter
what platform they're on. As long as the Drupal library/implementation
stays up on current best practices and behaviors, then there's no
reason to continue this discussion and push for Drupal to use the
JanRain libraries.
Chris
On 5/4/07, Dries Buytaert <dries at buytaert.net> wrote:
>
> On 03 May 2007, at 21:00, Chris Messina wrote:
> > Can you expand on what you didn't like. You're certainly fine to write
> > your own, but we're openly wondering whether another PHP
> > implementation really makes sense or if we can tweak the existing
> > library to better fit your needs.
> >
> > If not, no problem.
>
> Well, last time we checked the OpenID library, it was big. If I
> remember correctly, the OpenID library shipped with its own database
> abstraction layer, its own input sanitizing, etc, etc. A framework
> like Drupal already provides all of that functionality and we didn't
> want to duplicate that. Our current open ID module is 10 KB rather
> than 290 KB (in zipped format). I think Drupal itself is 650 KB.
>
> --
> Dries Buytaert :: http://www.buytaert.net/
>
>
--
Chris Messina
Citizen Provocateur &
Open Source Ambassador-at-Large
Work: http://citizenagency.com
Blog: http://factoryjoe.com/blog
Cell: 412 225-1051
Skype: factoryjoe
This email is: [ ] bloggable [X] ask first [ ] private
More information about the general
mailing list