To be clear, the current protocol spec assigns NO SEMANTICS to the oauth_version parameter. Implementations are free to fail in arbitrarily bizarre ways if you pass anything other than oauth_version=1.0 given that it is undefined. Given this, what good can come of changing it? You have no guarantees for how older clients and servers will behave in the presence of a new version number.
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
