blocks|key|1428379|text|它不是运行代码意义上的实现，但我真的很喜欢InfoQ上的文章"How+to+GET+a+cup+of+coffee“。它将在星巴克订购咖啡的过程描述为RESTful协议。本文超越了典型的“一切都是资源”的REST介绍性文章，并重点介绍了HATEOAS。强烈推荐。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1428380|entityMap|0|LINK|mutability|MUTABLE|url|http://www.infoq.com/articles/webber-rest-workflow^0|V|Q|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Its not an implementation in the sense of running code, but I really like the article "<a href="http://www.infoq.com/articles/webber-rest-workflow" rel="noreferrer">How to GET a cup of coffee</a>" on InfoQ. It describes the process of ordering a coffee at Starbucks as a RESTful protocol. This goes beyond the typical "everything is a resource" REST introductory article and focuses on HATEOAS. Highly recommended.

blocks|key|4344305|text|那Sun+Cloud+API呢？引言部分：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4344306|4344307|该应用编程接口假定URI空间中没有特定的结构。起始点是由云服务提供商提供的URI，它标识云本身。云的表示包含云中其他资源的URI，以及可能在这些资源上执行的操作(例如，部署和启动虚拟机)。|blockquote|4344308|4344309|4344310|backstory可能也会有所帮助。|4344311|entityMap|0|LINK|mutability|MUTABLE|url|https://web.archive.org/web/20190910062142/https://www.klariti.com/technical-writing/2016/11/09/examples-of-rest-api-documentation/|1|https://web.archive.org/web/20170123002223/http://blogs.oracle.com/craigmcc/entry/why_hateoas^0|1|D|0|0|0|0|0|0|0|9|1|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|10|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|11|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|12|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|13|8|@]|9|@$A|14|B|15|1|16]]|C|$]]|$1|L|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]|T|$5|O|P|Q|C|$R|U]]]]

How about the <a href="https://web.archive.org/web/20190910062142/https://www.klariti.com/technical-writing/2016/11/09/examples-of-rest-api-documentation/" rel="nofollow noreferrer">Sun Cloud API</a>? From the introduction:
<blockquote>
The API presupposes no particular structure in the URI space. The starting point is a URI, supplied by the cloud service provider, which identifies the cloud itself. The cloud's representation contains URIs for the other resources in the cloud, and also for operations which may be performed upon them (for example deploying and starting virtual machines).
</blockquote>
The <a href="https://web.archive.org/web/20170123002223/http://blogs.oracle.com/craigmcc/entry/why_hateoas" rel="nofollow noreferrer">backstory</a> might also be helpful.

blocks|key|4344381|text|Netflix有一个基于HATEOAS的REST+API，它将链接作为资源的一部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4344382|entityMap|0|LINK|mutability|MUTABLE|url|https://netflix.github.io/genie/docs/3.0.0/rest/^0|K|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Netflix has a <a href="https://netflix.github.io/genie/docs/3.0.0/rest/" rel="nofollow noreferrer">REST API</a> based on HATEOAS that includes links as part of the resources.

blocks|key|1127691|text|Sun+Cloud+API的RESTfulness实际上不是在Roy的第四点中解决的吗：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1127692|1127693|+REST+API不能定义固定的资源名称或层次结构(客户端和服务器的明显耦合)。服务器必须能够自由地控制自己的命名空间。相反，允许服务器指示客户端如何构造适当的URI，例如在HTML表单和URI模板中，通过在媒体类型和链接关系中定义这些指令。这里的失败意味着客户端由于带外信息而采用资源结构，例如特定于域的标准，这是RPC的功能耦合的面向数据的等价物。|blockquote|1127694|1127695|1127696|示例1在定义的继承性中固定的资源名称：|offset|length|style|BOLD|1127697|来自Sun+Cloud+API："...+VDC的表示将包括驻留在其中的集群的表示，这反过来又包括每个集群中的VM的表示。“|1127698|示例2带外信息，例如特定于域的标准：|1127699|您必须拥有wiki页面内容(带外信息)才能知道云资源字段"uri“的”资源通信机制“是GET。|1127700|entityMap^0|0|0|0|0|0|0|B|0|0|0|3|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|X|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|10|8|@$J|11|K|12|L|M]]|9|@]|A|$]]|$1|N|3|O|5|6|7|13|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|14|8|@$J|15|K|16|L|M]]|9|@]|A|$]]|$1|R|3|S|5|6|7|17|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|U|$]]

Isn't the RESTfulness of Sun Cloud API actually addressed in Roy's 4th point:

<blockquote>
 A REST API must not define fixed resource names or hierarchies (an obvious coupling of client and server). Servers must have the freedom to control their own namespace. Instead, allow servers to instruct clients on how to construct appropriate URIs, such as is done in HTML forms and URI templates, by defining those instructions within media types and link relations. [Failure here implies that clients are assuming a resource structure due to out-of band information, such as a domain-specific standard, which is the data-oriented equivalent to RPC's functional coupling].
</blockquote>

Example 1 Fixed resource names in a defined heirachy: 

From the Sun Cloud API: "... the representation of a VDC will include representations of the Clusters which inhabit it, which in turn include representations of the VMs within each cluster."

Example 2 out-of-band information, such as a domain-specific standard: 

You have to have the wiki-page contents (out-of-band information) to know that the "resource communication mechanism" for the Cloud resource field "uri" is GET.

blocks|key|4344448|text|我意识到不久前有人问过这个问题，但我尝试通过一个简单的示例来演示一个“适当的”REST+API流程。我试着遵循罗伊的休息规则--也许这会有所帮助：API+Example+using+REST|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4344449|entityMap|0|LINK|mutability|MUTABLE|url|http://thereisnorightway.blogspot.com/2012/05/api-example-using-rest.html^0|21|M|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I realized this was asked a while ago, but I took a stab at demonstrating a "proper" REST API flow for a simple example. I tried to follow Roy's rules for REST - perhaps it could help:
<a href="http://thereisnorightway.blogspot.com/2012/05/api-example-using-rest.html" rel="nofollow">API Example using REST</a>

as everyone may have noticed, there are lot of fake/rudimentary REST-APIs in the wild (which implement a HTTP-API and call it REST without following the hypertext-as-the-engine-of-application-state requirement, which led to the <a href="http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven" rel="noreferrer">famous rant of Roy T. Fielding</a>, the man who first specified the REST-paradigm).

I've been unable to find any practical examples of a truly hypertext driven REST-implementation along with the associated application-specific media-type definitions for the state transitions.

Are there any publicly accessible examples of such implementations?

Actual examples for HATEOAS (REST-architecture)

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

正如每个人可能已经注意到的，在野外有很多伪/基本的REST -API(它们实现了一个HTTP-API并将其称为REST，而不遵循超文本作为应用程序状态的引擎的要求，这导致了，他是第一个指定REST范式的人)。我找不到任何真正超文本驱动的REST实现的实际示例，以及状态转换的相关特定于应用程序的媒体类型定义。是否有可公开访问的此类实现的示例？

问HATEOAS (REST-架构)的实际示例
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问HATEOAS (REST-架构)的实际示例EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问HATEOAS (REST-架构)的实际示例
EN