blocks|key|1385123|text|这就是它可能看起来的样子。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1385124|创建具有以下三个属性的用户：|1385125|POST+/user
fname=John&lname=Doe&age=25|code-block|syntax|javascript|1385126|服务器响应：|1385127|200+OK
Location:+/user/123|1385128|将来，您可以检索用户信息：|1385129|GET+/user/123|1385130|1385131|200+OK
<fname>John</fname><lname>Doe</lname><age>25</age>|1385132|要修改记录(lname和age将保持不变)：|offset|length|style|CODE|1385133|PATCH+/user/123
fname=Johnny|1385134|要更新记录(因此lname和age将为空)：|1385135|PUT+/user/123
fname=Johnny|1385136|entityMap^0|0|0|0|0|0|0|0|0|0|6|5|C|3|0|0|8|5|E|3|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|19|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|1A|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|1B|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|1C|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|1D|8|@]|9|@]|A|$G|H]]|$1|Q|3|J|5|6|7|1E|8|@]|9|@]|A|$]]|$1|R|3|S|5|F|7|1F|8|@]|9|@]|A|$G|H]]|$1|T|3|U|5|6|7|1G|8|@$V|1H|W|1I|X|Y]|$V|1J|W|1K|X|Y]]|9|@]|A|$]]|$1|Z|3|10|5|F|7|1L|8|@]|9|@]|A|$G|H]]|$1|11|3|12|5|6|7|1M|8|@$V|1N|W|1O|X|Y]|$V|1P|W|1Q|X|Y]]|9|@]|A|$]]|$1|13|3|14|5|F|7|1R|8|@]|9|@]|A|$G|H]]|$1|15|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]]|16|$]]

This is what it might look like.

Create a user with three properties:

<pre><code>POST /user
fname=John&amp;lname=Doe&amp;age=25
</code></pre>

The server responds:

<pre><code>200 OK
Location: /user/123
</code></pre>

In the future, you can then retrieve the user information:

<pre><code>GET /user/123
</code></pre>

The server responds:

<pre><code>200 OK
&lt;fname&gt;John&lt;/fname&gt;&lt;lname&gt;Doe&lt;/lname&gt;&lt;age&gt;25&lt;/age&gt;
</code></pre>

To modify the record (<code>lname</code> and <code>age</code> will remain unchanged):

<pre><code>PATCH /user/123
fname=Johnny
</code></pre>

To update the record (and consequently <code>lname</code> and <code>age</code> will be NULL):

<pre><code>PUT /user/123
fname=Johnny
</code></pre>

blocks|key|1384882|text|REST使用各种HTTP方法(主要是GET/PUT/DELETE)操作数据。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1384883|您可以向/user/[id]+URL发送delete请求、编辑用户、检索有关您向/user/[id]发送GET请求的用户的信息，而不是使用特定的URL来删除方法(比如/user/123/delete|offset|length|style|CODE|1384884|例如，一组可能如下所示的URL。|1384885|GET+/delete_user.x?id=123
GET+/user/delete
GET+/new_user.x
GET+/user/new
GET+/user?id=1
GET+/user/id/1|code-block|syntax|javascript|1384886|你使用HTTP“动词”并且有..|1384887|GET+/user/2
DELETE+/user/2
PUT+/user|1384888|entityMap^0|0|4|A|14|A|2B|G|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@$D|W|E|X|F|G]|$D|Y|E|Z|F|G]|$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|13|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|15|8|@]|9|@]|A|$M|N]]|$1|S|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|T|$]]

REST is using the various HTTP methods (mainly GET/PUT/DELETE) to manipulate data.

Rather than using a specific URL to delete a method (say, <code>/user/123/delete</code>), you would send a DELETE request to the <code>/user/[id]</code> URL, to edit a user, to retrieve info on a user you send a GET request to <code>/user/[id]</code>

For example, instead a set of URLs which might look like some of the following..

<pre><code>GET /delete_user.x?id=123
GET /user/delete
GET /new_user.x
GET /user/new
GET /user?id=1
GET /user/id/1
</code></pre>

You use the HTTP "verbs" and have..

<pre><code>GET /user/2
DELETE /user/2
PUT /user
</code></pre>

blocks|key|1599661|text|它是一种编程，在这种编程中，您的系统架构适合Roy+Fielding在his+thesis中提出的REST+style。由于这是描述web的架构风格(或多或少)，所以很多人对它感兴趣。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1599662|额外的答案是:不。除非你把软件架构作为一门学术或设计web服务来研究，否则你真的没有理由去听这个术语。|1599663|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm|1|http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm^0|Z|A|0|1D|A|1|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

It's programming where the architecture of your system fits the <a href="http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm" rel="noreferrer">REST style</a> laid out by Roy Fielding in <a href="http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm" rel="noreferrer">his thesis</a>. Since this is the architectural style that describes the web (more or less), lots of people are interested in it.

Bonus answer: No. Unless you're studying software architecture as an academic or designing web services, there's really no reason to have heard the term.

blocks|key|1599922|text|如果我没有直接回答这个问题，我很抱歉，但是用更详细的例子来理解这一切会更容易。由于所有的抽象和术语，Fielding并不容易理解。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1599923|这里有一个相当好的例子：|1599924|Explaining+REST+and+Hypertext:+Spam-E+the+Spam+Cleaning+Robot|offset|length|1599925|更好的是，这里有一个简洁的解释和简单的例子(+powerpoint更全面，但你可以在html版本中获得大部分)：|1599926|http://www.xfront.com/REST.ppt或http://www.xfront.com/REST.html|1599927|读完示例后，我可以理解为什么Ken说REST是超文本驱动的。我不确定他是否正确，因为/user/123是一个指向资源的URI，我不清楚它是否是unRESTful，仅仅因为客户端知道它是“带外的”。|1599928|该xfront文档解释了REST和SOAP之间的区别，这也非常有帮助。当Fielding说"That+is+RPC.+It+screams+RPC.“时，很明显RPC不是RESTful，所以看看确切的原因是很有用的。(SOAP是RPC的一种类型。)|1599929|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ldodds.com/blog/archives/000337.html|1|http://www.xfront.com/REST.ppt|2|http://www.xfront.com/REST.html|3|http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven^0|0|0|0|1P|0|0|0|0|U|1|V|V|2|0|0|1A|S|3|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@$F|16|G|17|1|18]]|A|$]]|$1|H|3|I|5|6|7|19|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1A|8|@]|9|@$F|1B|G|1C|1|1D]|$F|1E|G|1F|1|1G]]|A|$]]|$1|L|3|M|5|6|7|1H|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1I|8|@]|9|@$F|1J|G|1K|1|1L]]|A|$]]|$1|P|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]|X|$5|S|T|U|A|$V|Y]]|Z|$5|S|T|U|A|$V|10]]|11|$5|S|T|U|A|$V|12]]]]

I apologize if I'm not answering the question directly, but it's easier to understand all this with more detailed examples. Fielding is not easy to understand due to all the abstraction and terminology.

There's a fairly good example here:

<a href="http://www.ldodds.com/blog/archives/000337.html" rel="noreferrer">Explaining REST and Hypertext: Spam-E the Spam Cleaning Robot</a>

And even better, there's a clean explanation with simple examples here (the powerpoint is more comprehensive, but you can get most of it in the html version):

<a href="http://www.xfront.com/REST.ppt" rel="noreferrer">http://www.xfront.com/REST.ppt</a> or <a href="http://www.xfront.com/REST.html" rel="noreferrer">http://www.xfront.com/REST.html</a>

After reading the examples, I could see why Ken is saying that REST is hypertext-driven. I'm not actually sure that he's right though, because that /user/123 is a URI that points to a resource, and it's not clear to me that it's unRESTful just because the client knows about it "out-of-band."

That xfront document explains the difference between REST and SOAP, and this is really helpful too. When Fielding says, "<a href="http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven" rel="noreferrer">That is RPC. It screams RPC.</a>", it's clear that RPC is not RESTful, so it's useful to see the exact reasons for this. (SOAP is a type of RPC.)

blocks|key|1599840|text|我看到一堆答案，说把关于用户123的所有东西放在资源"/+user+/123“上就是RESTful。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1599841|创造了这个术语的罗伊·菲尔丁说，REST+APIs+must+be+hypertext-driven。特别是，“REST+API不能定义固定的资源名称或层次结构”。|offset|length|1599842|因此，如果您的"/user/123“路径是在客户机上硬编码的，那么它就不是真正的RESTful。很好的使用HTTP，也许是，也许不是。但不是RESTful。它必须来自超文本。|1599843|entityMap|0|LINK|mutability|MUTABLE|url|http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven^0|0|G|Y|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

I see a bunch of answers that say putting everything about user 123 at resource "/user/123" is RESTful.

Roy Fielding, who coined the term, says <a href="http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven" rel="noreferrer">REST APIs must be hypertext-driven</a>. In particular, "A REST API must not define fixed resource names or hierarchies".

So if your "/user/123" path is hardcoded on the client, it's not really RESTful. A good use of HTTP, maybe, maybe not. But not RESTful. It has to come from hypertext.

blocks|key|1385190|text|REST是一种编写分布式应用程序的架构模式和风格。它不是狭义的编程风格。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1385191|说你使用REST风格，就像说你用一种特定的风格建造了一座房子:例如，都铎风格或维多利亚风格。作为软件风格的REST和作为家庭风格的都铎或维多利亚风格都可以由组成它们的质量和约束来定义。例如，REST必须具有Client+Server分离，其中消息是自描述的。都铎风格的房屋有重叠的山墙和屋顶，屋顶陡峭倾斜，前面有山墙。你可以阅读Roy的论文来了解更多关于构成REST的约束和质量。|1385192|与家庭风格不同的是，REST很难得到一致和实际的应用。这可能是故意的。将其实际实现留给设计者。因此，您可以自由地做您想做的事情，因此，只要您满足了论文中提出的约束条件，您就可以创建REST系统。|1385193|奖励：|1385194|整个web都是基于REST的(或者说REST是基于web的)。因此，作为一名web开发人员，您可能希望意识到这一点，尽管编写好的web应用程序并不是必须的。|1385195|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

REST is an architectural pattern and style of writing distributed applications. It is not a programming style in the narrow sense.

Saying you use the REST style is similar to saying that you built a house in a particular style: for example Tudor or Victorian. Both REST as an software style and Tudor or Victorian as a home style can be defined by the qualities and constraints that make them up. For example REST must have Client Server separation where messages are self-describing. Tudor style homes have Overlapping gables and Roofs that are steeply pitched with front facing gables. You can read Roy's dissertation to learn more about the constraints and qualities that make up REST.

REST unlike home styles has had a tough time being consistently and practically applied. This may have been intentional. Leaving its actual implementation up to the designer. So you are free to do what you want so as long as you meet the constraints set out in the dissertation you are creating REST Systems.

Bonus:

The entire web is based on REST (or REST was based on the web). Therefore as a web developer you might want aware of that although it's not necessary to write good web apps.

blocks|key|1600160|text|REST+===+HTTP类比是不正确的，除非您不强调它“必须”是HATEOAS驱动的事实。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1600161|罗伊自己清除了它here。|1600162|在输入REST+API时，除了初始URI+(书签)和一组适用于目标受众的标准化媒体类型(即，任何可能使用该API的客户端都应能理解)之外，不应事先了解其他内容。从那时起，所有应用程序状态转换都必须由客户端对服务器提供的选择的选择驱动，这些选择出现在接收到的表示中，或者由用户对这些表示的操作所暗示。转换可以由客户端对媒体类型和资源通信机制的知识来确定(或受其限制)，这两者都可以在运行中(例如，按需编码)得到改进。|1600163|这里的失败意味着带外信息正在驱动交互，而不是超文本。|1600164|entityMap|0|LINK|mutability|MUTABLE|url|http://restfulapi.net/hateoas/|1|http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven^0|X|7|0|0|8|4|1|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]]]

REST === HTTP analogy is not correct until you do not stress to the fact that it "MUST" be <a href="http://restfulapi.net/hateoas/" rel="noreferrer">HATEOAS</a> driven. 

Roy himself cleared it <a href="http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven" rel="noreferrer">here</a>.

A REST API should be entered with no prior knowledge beyond the initial URI (bookmark) and set of standardized media types that are appropriate for the intended audience (i.e., expected to be understood by any client that might use the API). From that point on, all application state transitions must be driven by client selection of server-provided choices that are present in the received representations or implied by the user’s manipulation of those representations. The transitions may be determined (or limited by) the client’s knowledge of media types and resource communication mechanisms, both of which may be improved on-the-fly (e.g., code-on-demand). 

[Failure here implies that out-of-band information is driving interaction instead of hypertext.]

blocks|key|1600076|text|rest的要点是，如果我们同意使用一种公共语言进行基本操作(+http动词)，则可以将基础架构配置为理解它们并适当地优化它们，例如，通过使用缓存头来实现所有级别的缓存。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1600077|通过正确实现restful+GET操作，无论信息来自服务器的DB、服务器的memcache、CDN、代理的缓存、浏览器的缓存还是浏览器的本地存储，都无关紧要。可以使用最快的、最容易获得的最新源代码。|1600078|说Rest只是从使用带有操作参数的GET请求到使用可用的http动词的语法更改，这让它看起来没有任何好处，纯粹是表面上的。重点是使用一种可以被链中的每一部分理解和优化的语言。如果GET操作具有副作用的操作，则必须跳过所有HTTP缓存，否则将得到不一致的结果。|1600079|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The point of rest is that if we agree to use a common language for basic operations (the http verbs), the infrastructure can be configured to understand them and optimize them properly, for example, by making use of caching headers to implement caching at all levels.

With a properly implemented restful GET operation, it shouldn't matter if the information comes from your server's DB, your server's memcache, a CDN, a proxy's cache, your browser's cache or your browser's local storage. The fasted, most readily available up to date source can be used.

Saying that Rest is just a syntactic change from using GET requests with an action parameter to using the available http verbs makes it look like it has no benefits and is purely cosmetic. The point is to use a language that can be understood and optimized by every part of the chain. If your GET operation has an action with side effects, you have to skip all HTTP caching or you'll end up with inconsistent results.

blocks|key|1600189|text|我想说，理解REST的一个重要构建块在于端点或映射，例如/customers/{id}/balance。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1600190|您可以将这样一个端点想象为从网站(前端)到数据库/服务器(后端)的连接管道。使用它们，前端可以执行在应用程序中任何REST映射的相应方法中定义的后端操作。|1600191|entityMap^0|S|N|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

I would say that an important building block in understanding REST lies in the endpoints or mappings, such as <code>/customers/{id}/balance</code>.

You can imagine such an endpoint as being the connecting pipeline from the website (front-end) to your database/server (back-end). Using them, the front-end can perform back-end operations which are defined in the corresponding methods of any REST mapping in your application.

blocks|key|1600225|text|REST+API是遵循REST架构约束的API实现。它充当一个接口。客户端和服务器之间的通信是通过HTTP进行的。REST+API利用HTTP方法在客户端和服务器之间建立通信。REST还允许服务器缓存响应，从而提高应用程序的性能。客户端和服务器之间的通信是一个无状态的过程。我的意思是，客户端和服务器之间的每一次通信都像是一个新的通信。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1600226|没有从以前的通信中携带的信息或记忆。因此，每次客户端与后端交互时，都必须将身份验证信息发送给后端。这使后端能够确定客户端是否有权访问数据。|1600227|通过实现REST+API，客户端获得要与之通信的后端端点。这完全解耦了后端&客户端代码。|1600228|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

A REST API is an API implementation that adheres to the REST architectural constraints. It acts as an interface. The communication between the client &amp; the server happens over HTTP. A REST API takes advantage of the HTTP methodologies to establish communication between the client and the server. REST also enables servers to cache the response that improves the performance of the application.
The communication between the client and the server is a stateless process. And by that, I mean every communication between the client and the server is like a new one.

There is no information or memory carried over from the previous communications. So, every time a client interacts with the backend, it has to send the authentication information to it as well. This enables the backend to figure out that the client is authorized to access the data or not.

With the implementation of a REST API the client gets the backend endpoints to communicate with. This entirely decouples the backend &amp; the client code.

问RESTful编程到底是什么？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问RESTful编程到底是什么？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问RESTful编程到底是什么？
EN