Spring Social 和 Facebook API 变更
我正在考虑使用 Spring Social 与 Facebook 集成，但我以前从未与它进行过任何类型的集成，所以这看起来不错。我唯一担心的是，如果 Facebook 经常更改他们的 API，那么我们似乎必须等待 Spring Social 更新。不幸的是，由于这个项目没有使用 Maven，那会更痛苦。
还有其他人认为这是一个问题吗？即 Facebook 是否对其 API 进行了足够的更改，以至于成为一个问题，或者是否存在较长的弃用/向后兼容期，以便为 Spring Social 提供时间来更新其 API？
I'm thinking of using Spring Social to integrate with Facebook, but I've never done any kind of integration with it before, so this seems nice. My only worry is if the Facebook changes their API somewhat often, it seems like we would have to wait for Spring Social to be updated. Since this project unfortunately doesn't use Maven, that would be even more of a pain.
Does anyone else find this to be an issue, i.e. does Facebook alter its API enough for it to be a problem, or is there a large deprecation/backwards-compatibility period in order to give Spring Social time to update their API?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
Facebook 喜欢一直改变和破坏他们的 API，而且他们不关心他们的开发人员。对于某些更改，他们会提前通知人们（仅当您经常查看他们的博客时），以便第 3 方 SDK 可以有机会更新，但对于他们宣布的每一项重大更改，我可以列出他们未宣布的重大更改（只需注意他们每周确认的错误数量和已修复的错误数量几乎翻倍即可）。
Facebook likes to change and break their API all the time and they don't care for their developers. On some of the changes they will give people advance notice (only if you check their blog very frequently) so 3rd party SDK's can have a chance to update but for every breaking change they announce, I could name a breaking change they didn't announce (just notice how they confirm nearly double the amounts of bugs each week and bugs that get fixed).