> > CakeBaker: any chance you've got plans to update your Component? > > No, there are no plans to integrate support for RPX into the OpenID > component, because support for a proprietary API doesn't fit to the > current functionality of the OpenID component. I think it is better to > put the RPX functionality into its own component.
After I sent the message to the group I implemented RPXnow last night and I agree with you completely in this doesn't belong or fit well with your component. Actually I'm not sure it even requires its own component. There is so very little code to make it work and to integrate it into your existing users I think a clean example would be more useful. Now I can authenticate via the legacy Cake Auth, I can authenticate via the OpenID Component (Great component by the way) and I can authenticate via RPXnow. I think the problem with OpenID is its still a little immature and if I provide enough UI to help those who don't understand what an OpenID URL is, my login page starts to look like a bunch of random sponsor links. However I'll take that over the 100's of username/passwords I have for all those sites visit. ;) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
