跨多个组织的长期存在的基于网络的应用程序在 REST 中意味着什么? [英] What does long-lived network-based applications that span multiple organizations means in REST?

问题描述

我看了很多教程来了解 REST 的所有内容.

I came across many tutorials to understand each and everything of REST.

我的理解 - REST 是一种基于网络的应用程序的架构风格(我的意思是服务器为客户端提供服务，并且两者都基于网络相互通信)

My Understanding - REST is an architectural style for network-based applications (I mean service available for a client by the server and both communicate each other based on the network)

我的理解有误吗?

根据 Roy T Fielding 的说法，跨多个组织的长期基于网络的应用程序意味着什么 在 REST 中https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven#comment-742

What exactly long-lived network-based applications that span multiple organizations means in REST according to Roy T Fielding https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven#comment-742

我对术语长期存在的基于网络的应用程序感到困惑.

I am confused with the term long-lived network-based applications.

因此，如果我创建的 API 遵循 REST 的约束但在网络上不可用，但可以在网络内访问(例如，一个用于获取学校学生分数但在互联网上不可用的 API，只是在学校内可用并通过 HTTP://SERVERIP 访问)-这不能是 REST API 吗?

So if I create an API which follows constraints of REST but not available on the web, but can be accessed within a network (For example, an API to get marks of students in a school but not available in the internet, just available within the school and accessed through HTTP://SERVERIP) - is this cannot be a REST API?

推荐答案

这不能是 REST API 吗?

is this cannot be a REST API?

不，没关系.

其中一个关键思想是:我们对客户端和服务器之间的自描述消息达成了一致的标准.在 Web 的情况下，该标准是 HTTP.HTTP 是(在大多数情况下；参见 第六章 对于某些例外情况)旨在满足 REST 架构约束.由于我们拥有该标准，因此我们可以通过反向代理(由 Apache 软件基金会实施)将浏览器(由 Google 实施)指向 Web 服务器(由 Oracle 实施)，并且一切正常工作".

One of the key ideas is this: that we have an agreed upon standard for the self descriptive messages between the client and server. In the case of the Web, that standard is HTTP. HTTP was (for the most part; see chapter six for some exceptions) designed to satisfy the REST architectural constraints. Because we have that standard, we can point a browser (implemented by Google) at a web server (implemented by Oracle) via a reverse proxy (implemented by the Apache Software Foundation) and it all "just works".

如果你把这些碎片放到一个你控制的隔离网络上，它仍然正常工作".

If you take those pieces, and put them onto an isolated network that you control, it still all "just works".

长命百岁是什么意思，请...

what does long-lived means in layman terms, please...

Roy 隐藏了他对此的解释 在评论中.

Roy buried his explanation for that in the comments.

REST 是数十年规模的软件设计:每一个细节都旨在促进软件寿命和独立发展.

REST is software design on the scale of decades: every detail is intended to promote software longevity and independent evolution.

网络上的几乎所有内容都理解 HTTP/1.1 (1999)，它建立在 HTTP/1.0 (1996) 之上，而 HTTP/1.0 (1996) 又建立在 HTTP/0.9 (1991).

Pretty much everything on the web understands HTTP/1.1 (1999), which builds upon HTTP/1.0 (1996), which in turn builds on HTTP/0.9 (1991).

这篇关于跨多个组织的长期存在的基于网络的应用程序在 REST 中意味着什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！