Thoughts on the next version of foursquareCFC, please comment!

Filed under: foursquareCFC

comments (0) Views: 4,872

I'm in the initial stages of updating foursquareCFC to use foursquare's API 2.0 and I wanted your input on something.

With this new release, foursquare has moved from a username and password access method to oAuth. The premise is that while the user is interacting with some web, or mobile, application they'll be asked to authenticate. Then, instead of providing their credentials to the requester, they'll be redirected to foursquare to login, and redirected back to the application with an oAuth token. I'm sort of feeling like my library needs to just require the token when being instantiated and that's that. I'm interested to hear the viewpoints of some of you though. Should I bother doing the authentication in this library or require it in advance?

Amazon logo

If this article was interesting, or helpful, or even wrong, please consider leaving a comment, or buying something from my wishlist. It's appreciated!

comments powered by Disqus