I wanted to follow up on this.  Admittedly, I'm a newb with oauth.
I'm currently working on an application that uses MS's cloud computing
environment Azure.  I'm using this to schedule tweets in the future.
Azure has a worker role which is an application that a web user never
directly works against.  The worker role is being used to post updates
to a user's stream.  Right now, I am using basic auth, but I would
like to move to oauth.  My current design has the user storing
twitterids and passwords in a table.  The user interacts over the web
with the webrole and then the worker role handles the posting.

It looks to me, given a VERY limited knowledge of oauth, that its
designed with user interaction in mind.  Does that sound correct?

Wally

Reply via email to