I've finally mastered OAuth! I think that someone not integrally tied to the OAuth project should write a tutorial about it - someone unencumbered by the history of the project that can focus on just what you need to know. The biggest problem for me was reading the spec which just didn't present the information in the way that my brain learns. Right now, I think that implementing OAuth rather than basic authentication is a daunting choice. With one, your efforts are trivial while the other can mean days of struggles. Get something wrong, and nothing works with hardly anything to go on. It takes lots of patience to find the problems.
While I started with some libraries I found out there, I ended up doing my own consumer-side (client-side) implementation simply because I needed a framework for understanding what was happening going back and forth. If I have time, I might release my implementation. It is mostly written in JavaScript and handles the complete dance, starting with the consumer key, through to the request token, verifier code, and finally winds up with the access token given out by twitter. -- You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oa...@googlegroups.com. To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/oauth?hl=en.
