Please don't make any changes that are incompatible with existing applications of the net.oauth library.
Since OAuth 1 and OAuth 2 use conflicting terminology, I recommend creating a new package net.oauth.v2. For example, you can create the class net.oauth.v2.OAuthClient, with minimal confusion with the existing net.oauth.OAuthClient. I haven't thought about it much, but I suspect it might be best to create an entirely new API for OAuth 2. I don't see much overlap with OAuth 1. What has been the experience of people who have implemented OAuth 2? Does a combined API make sense? -- You received this message because you are subscribed to the Google Groups "OAuth" 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/oauth?hl=en.
