Bill Shupp [2010-09-25 18:03 UTC] HTTP_OAuth already provides both consumer and provider support. I've also started on a storage interface for it. I don't see a need for a new package, when the existing one can simply be improved (yours provides 2 legged support).
Why is this package necessary?
Till Klampaeckel [2010-09-25 19:58 UTC] If your package shares so much in common with HTTP_OAuth, maybe you could contribute to the existing package instead?
Till
Tetsuya Yoshida [2010-09-26 12:53 UTC] I think sharing HTTP_OAuth is best.
But, it is difficult to improve.
I give priority to implementing RSA-SHA1.
To implementing RSA-SHA1, existing code cannot be made the best use of for extensive modifications are necessary.
For instance, it is necessary to change HTTP/OAuth/Provider/Request.php and HTTP/OAuth/Signature/*.
There is a possibility that the usage of an existing method changes, and confusion might be given to the user.
So, I propose HTTP_OAuthProvider.
Yoshida
|
