为HATEOAS（REST的架构）的实际例子 [英] Actual examples for HATEOAS (REST-architecture)

问题描述

因为大家可能已经注意到，有（有很多假的/基本的REST的API在野外它们实现一个HTTP的API，并称之为REST而不遵循超文本作为最引擎的应用程序状态的要求，这就导致了著名罗伊·菲尔丁吨的咆哮中的谁第一个指定的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?

推荐答案

它不是在运行code意义上的实现，但是我真的很喜欢文章的如何获得咖啡一杯InfoQ上。它描述订购星巴克咖啡为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屋！