[twitter-dev] OAUTH on J2ME forums

2010-09-06 Thread Amid Lad
hi all.
i'm building an application in j2me.
but, i get stuck on oauth.
should i get request token everytime user want to login ?
should user enter pin code everytime ?
should i get access token everytime ?

if no, how to authenticate user ? should i save the access token on my
database ?

thanks..

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en


Re: [twitter-dev] OAUTH on J2ME forums

2010-09-06 Thread Tom van der Woerdt
On 9/6/10 11:46 AM, Amid Lad wrote:
 hi all.
 i'm building an application in j2me.
 but, i get stuck on oauth.
 should i get request token everytime user want to login ?
 should user enter pin code everytime ?
 should i get access token everytime ?
 
 if no, how to authenticate user ? should i save the access token on my
 database ?
 
 thanks..

Consider the usertoken the username and the usersecret the password.
You should treat them like this: the usertoken isn't really a private
string, while the secret is very much like a password.

Just like with any other username and password, you can simply save them
and use them again. While an user can't change the password (secret), it
can revoke the keys.

Tom

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en