mkdynamic/omniauth-facebook — comment on commit 7bede2d4a1e6a4017449045ae4ac9bcee9d79204
File: README.md line 20
By mkdynamic:

I think #1 and #2 are basically the same, in terms of the performance. I think #2 is possibly slightly more convenient.

#3 would be quicker and closer to the true client-side flow since if you pass the access token (that you got from the hash) you can skip the access token request to FB on the server. I'm not sure if there are any security concerns with passing the access token back in this way. That's the main question in my mind.

I may end up impl. #2 to start off since it works the same as 0.3 gem and should hopefully provide the easiest upgrade path for folks...

On Nov 22, 2011, at 10:50 AM, David Kariuki wrote:

> Yes currently I'm just hitting `/auth/facebook` (I'm still on OmniAuth 0.3 with Devise). I'm not entirely sure but would #1 have any performance benefit?
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/mkdynamic/omniauth-facebook/commit/7bede2d4a1e6a4017449045ae4ac9bcee9d79204#commitcomment-738640