For Tweed for webOS, we have a perfectly fine OAuth implementation and most of our requests go through just fine (and have for a few months).
However, we get occasional 401s. After digging around a bit we found that correctly-signed requests can timeout on the server side and Twitter returns a 401. So we changed our code to, when it gets a 401 it will immediately retry the request one time. It seems that this approach isn't the best as we're still getting reports from the field that sometimes the requests fail with a 401, when we give the user a "your password is out of sync, please re-enter it" type of message. What is the *correct* behavior for a 401? thx, --dwf -- 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
