I am using the oauth-python-twitter from google code to establish oauth authentication with twitter from my django app. I don't use django oauth application as part of my solution cause i have no need, i only need a thin use of oauth to make a user of my app a follower of my twitter account. it's one time action per user request, create and forget. my problem is that i get a request token using the getRequestToken method then use it to redirect user to the authorization url. all this is done from one view. when service provider redirects user to my callback url (which is a new view) i am out of context already, and it only provides the oauth_token and not the oauth_token_secret. i need both to be able to ask for access token. i can save the secret locally but it feels it's not the appropriate way to use the oauth module, not to mention that creating an oauth.OAuthToken manually when using the oauth-python-twitter module is kinda crooked. (a mix and match)
any suggestions? i really want an advice on the correct way to use it between requests, some good practices. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
