Why do I use Facebook's JS SDK to create API calls .... that is, the FBPI method Use when I can just send the HttpRequest to any API call using the jQuery getJSON and return JSON very easily.
I think about the benefits of using FB.api that this cookie already already grabs and knows about the user's token? But then do not use the getJSON method if the very good part is getting back to parsing via JSON data. I can not think of any benefit beyond this unless such methods can be such as FB.api (). SomeMethod .
At this point I have to maintain and maintain the user's information in a cookie of JS-SDK, which is great, but if I can just use jQuery such that I have any If you have an API call after coming back for an API call with the other API, then do I have to stop it from Facebook?
Definitely use FB.api - as you mentioned Do their SDK handle all the tokens / session stuff for you.
And if you are worried about parsing JSON in the result handler. Just use jQuery.
Comments
Post a Comment