Mowser
The google-api-python-client has just added support for the client_secrets.json file format (in tip, a new release with the support is coming soon).
The file format is (loosely) defined here:
http://code.google.com/p/google-api-python-client/wiki/ClientSecrets
The oauth2client/google-api-python-client support is explained here:
http://code.google.com/p/google-api-python-client/wiki/ClientSecretsSupport
Copied from the 'Motivation' section:
Traditionally providers of OAuth endpoints have relied upon cut-and-paste as the way users of their service move the client id and secret from a registration page into working code. That can be error prone, along with it being an incomplete picture of all the information that is needed to get OAuth 2.0 working, which requires knowing all the endpoints and configuring a Redirect Endpoint. If service providers start providing a downloadable client_secrets.json file for client information and client libraries start consuming client_secrets.json then a large amount of friction in implementing OAuth 2.0 can be reduced.
2011-10-12
I'm giving Twitter another shot, this time at http://twitter.com/bitworking.
2011-05-31
The APIs Discovery Service launched today. This has been in the works for a while, but probably not a secret if you've been following checkins to the google-api-python-client library. The announcement went out on the Google Code blog, and has been covered in other venues.
Two things to add that haven't been covered so far, the first is that if someone besides Google were to build an API that could be described by the Discovery format, then potentially some of these libraries would work with that API. Secondly, check out that patent license. While the obvious questions will be raised, instead let's fill the comments with your theories of why we didn't use WADL.
2011-05-10
You are viewing a mobilized version of this site...
View original page here
Mowser