Hi John, Thank you for your comment.
Exactly there are some conflicting terminology. And it is pretty much annoying to implement that actually. So maybe you are right. I think that I better create a new packge for OAuth 2.0. (Actually I have never noticed there is already OAuthClient.java because I have never used consumer side library.) >From my understanding, as far as Web Server Flow, overlap is only redirecting flow after authentication from Authorization server. So it does not have to be a combined API. But I want to keep API same as before as much as possible so that it can be easy to implement OAuth2.0 provider for people who have implemented OAuth1.0 provider before. That is why I thought it was better to modify existing classes especially if they are in "common" project. Why do you think that it might be best to create an entirely new API for OAuth 2? Are there any other reason than little overlap in those versions? -- You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oa...@googlegroups.com. To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/oauth?hl=en.
