HATEOAS(REST 架构)的实际示例 [英] Actual examples for HATEOAS (REST-architecture)

问题描述

正如每个人可能已经注意到的那样，在野外有很多假的/基本的 REST-API(它们实现了一个 HTTP-API 并将其称为 REST，而不遵循超文本作为应用程序状态的引擎要求)，这导致了 Roy T. Fielding 的著名咆哮，第一个指定 REST 范式的人).

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 famous rant of Roy T. Fielding, the man who first specified the REST-paradigm).

我一直无法找到真正超文本驱动的 REST 实现的任何实际示例，以及用于状态转换的关联的特定于应用程序的媒体类型定义.

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?

推荐答案

它不是运行代码意义上的实现，但我真的很喜欢这篇文章如何喝杯咖啡".它将在星巴克订购咖啡的过程描述为 RESTful 协议.这超出了典型的一切都是资源"REST 介绍性文章，重点介绍 HATEOAS.强烈推荐.

Its not an implementation in the sense of running code, but I really like the article "How to GET a cup of coffee" 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.

这篇关于HATEOAS(REST 架构)的实际示例的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！