Facebook 何时弃用 JavaScript SDK？
我在 Facebook 开发者论坛上问过这个问题，但没有人回答，所以我想我应该在 Stack 上问这个问题。
我有一个网站，它使用 OAuth 进行身份验证与 Facebook Connect 集成。但我有一些利用 JavaScript SDK 的代码。
我听说 JavaScript SDK 已被弃用和/或通过 JavaScript SDK 进行的身份验证已被弃用。
任何人都可以：
- 确认上述声明是否属实
- 提供一个链接，给出该声明将被弃用的日期
- 告诉我我错了
编辑
对于任何好奇我为什么仍然使用 JavaScript SDK 的人，请参阅我的另一个堆问题进行推理。
简而言之，这不能通过 OAuth/Graph API 来完成：
FB.getLoginStatus(function (response) {
if (response.status == 'connected') {
// do single sign on, seamlessly.
}
}
I've asked this on the Facebook Developer Forums, but no-one is answering, so thought i'd ask it on Stack.
I've got a website which integrates with Facebook Connect using OAuth for authentication. But i have some code which leverages the JavaScript SDK.
I have heard that the JavaScript SDK is being deprecated and/or authentication via the JavaScript SDK is being deprecated.
Can anyone:
- Confirm if the above statement is true
- Provide a link giving the date that it is to be deprecated
- Tell me im wrong
EDIT
For anyone who is curious as to why i still use the JavaScript SDK, see my other Stack question for the reasoning.
In short, this cannot be done with OAuth/Graph API:
FB.getLoginStatus(function (response) {
if (response.status == 'connected') {
// do single sign on, seamlessly.
}
}
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
需要明确的是，我们不会弃用 JavaScript SDK。它就留在这里。我们正在将其更改为依赖 OAuth 2.0 ，但使用起来同样简单。如果您现在使用
access_token，那么变化将很小（一旦更新的 JS SDK 发布，基本上将session.access_token替换为authResponse.accessToken）。如果您依赖session_key和secret并使用基于 md5 签名的调用，那么您需要进行一些迁移，因为这些将在仅限 OAuth 2.0 的世界中消失。To be very clear, we are not deprecating the JavaScript SDK. It's here to stay. We are in the process of changing it to rely on OAuth 2.0, but it will be just as simple to use. If you use
access_tokentoday, then the changes will be minor (largely replacesession.access_tokenwithauthResponse.accessTokenonce the updated JS SDK is out). If you rely onsession_keyandsecretand use md5 signature based calls, then you have some migrating to do since those will go away in the OAuth 2.0 only world.迁移到 OAuth 2.0 + HTTPS 时间表：
http://developers.facebook.com/blog/post/497
http://developers.facebook.com/docs/authentication/connect_auth/
Migration to OAuth 2.0 + HTTPS timeline:
http://developers.facebook.com/blog/post/497
http://developers.facebook.com/docs/authentication/connect_auth/
旧版 SDK 已被弃用，但仍可供您使用。 但是您确实应该考虑迁移到新的SDK。
目前最新的PHP-SDK在鉴权实现上与JS不同步；他们将在不久的将来对这两个 SDK 进行一些更改，以统一一些例程。
The older SDK is already deprecated but will be available for you to use. But you should really think about migrating to the new SDK.
Currently the latest PHP-SDK is out of sync in terms of authentication implementations with JS; they will be rolling out few changes to both of the SDK's in the near future to unify some of the routines.
当前的 javascript SDK 绝对不会被弃用。也许他们会弃用旧的 Facebook connect javascript，但他们还没有宣布日期。了解弃用日期的最佳位置是 Facebook 开发者路线图。
The current javascript SDK definitely isn't being deprecated. Perhaps they will deprecate the old Facebook connect javascript, but they haven't announced a date. The best place for deprecation dates is the Facebook developer roadmap.