您最想复制或最受欢迎的 Web API 是什么？
Soap、REST、xmlrpc。 Facebook、Twitter、[插入 Web 2.0 网站]。 什么是最终的 Web API？您最有可能在自己的代码中复制哪个 API？出于什么原因？ 似乎有些 Web API 会引起开发人员的恶心，而另一些则引起纯粹的崇拜。 如果你被告知要为一个网站/产品开发一个 API，你会效仿哪个（即使它有点过分）？
Soap, REST, xmlrpc. Facebook, twitter, [insert web 2.0 site]. What is the definitive web API and which would be the one that you would most likely replicate in your own code and for what reason? It seems that some web APIs invoke nausea in developers while other invoke pure worship. If you were told to develop an API for a website/product which would you emulate (even if it was overkill)?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
37signals 的产品拥有出色的 API，使用 RESTful XML-over-HTTP。 文档也相当不错。
Products from 37signals have great APIs, using RESTful XML-over-HTTP. The documentation is reasonably good, too.
HTTP 本身。
提供的原语具有表现力，但足够通用，可以应用于广泛的问题。 让我头发变白的 API 是对我将如何使用它们做出毫无根据的假设的 API。 HTTP 非常具有非规范性。
HTTP itself.
The primitives provided are expressive, yet general enough to be applied to a vast range of problems. The APIs that turn my hair grey are ones that make unwarrented assumptions about how I am going to use them. HTTP is beautifully non-prescriptive.
Google GDATA 的 API 集（我使用的是 YouTube 的 API）扩展了 Atom，它本身就是一个标准，因此花在使用它进行开发的时间也花在学习这种 RSS 类型的协议上，这使其比其他协议更具优势恕我直言，专有的。
The Google GDATA set of APIs - I use the YouTube one - extends Atom, which is a standard in its own right, so time spent developing with it is also time spent learning about this RSS-type protocol, which gives it an edge over more proprietary ones IMHO.
Flickr 的 API 相当不错： http://www.flickr.com/services/api/
花了几个月的时间使用它，发现它非常有用。 这些文档也很棒，很多都让它看起来更容易。
REST、JSON/XML/PHP/SOAP 协议，每个端点都是命名空间的，每个请求都有很多选项/参数。 错误消息和代码也被记录下来。
最重要的是，它可以让您访问 Flickr 存储的有关其照片和用户的几乎所有信息（当然，需要适当的权限）。 一定会喜欢好的 API！
Flickr's API is pretty good: http://www.flickr.com/services/api/
Spent a few months working with it and found it pretty usable. The docs are great too, which many have made it seem that much easier.
REST, JSON/XML/PHP/SOAP protocols, every endpoint is namespaced, lots of options/parameters for every request. Error messages and codes are documented too.
Most of all it lets you access just about all information Flickr stores about its photos and users (with appropriate permissions, of course). Gotta love good APIs!