> Since there is no clear "best practices" way on how to universally
> parse out the authorization code
I may be missing something here - are you talking about the oauth token
that's passed to your oauth callback page?
Can't that be accessed by parsing the GET parameters using any standard
url parsing library and taking the value of the "code" parameter? I've
not seen anywhere that documents any specific length of the token.
Tim Wintle
--
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To post to this group, send email to youtube-api-gdata@googlegroups.com.
To unsubscribe from this group, send email to youtube-api-gdata+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/youtube-api-gdata?hl=en.
No comments:
Post a Comment