Ernesto, How are you liking Go? I have been considering it. I would be more likely to consider it if I knew people outside of Google were using it since Google would never hire me for any meaningful position. -Brandon From: [email protected] [mailto:[email protected]] On Behalf Of Ernesto Oltra Sent: Sunday, January 08, 2012 3:07 PM To: [email protected] Subject: Re: [google-appengine] Re: Hardcoded access to a Google Data service from App Engine-app Hi, I didn't have any problems in sharing all the code, but it's in Go; contact me if you need it. I meant that the OAuth flow is: You prepare the authorization & redirect the user to Google ---> The user allows your app ---> Google gives you a temporary token ---> You interchange that token with a permanent one (with an expire date) ---> Store it Each time you do a request, the code must: Retrieve the token ---> If it's expired, ask for a new one -> Store it again if it has changed ---> Do the request Hard-coding the password in your code requires an update & deploy each time the user changes the password (apart from being less secure). Ernesto -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
-- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
