From e9e2c0343ef75fc39101601b4b9a7ce56e07f8c0 Mon Sep 17 00:00:00 2001 From: youmoo Date: Fri, 7 Aug 2015 14:11:03 +0800 Subject: [PATCH] Update 2015-05-01-graphql-introduction.md Or the alternative: `REST is an acronym for Representational State Transfer, which is an architectural style rather than a formal protocol`. Sorry , I'am not a native speaker:) --- _posts/2015-05-01-graphql-introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2015-05-01-graphql-introduction.md b/_posts/2015-05-01-graphql-introduction.md index 3a9603351..9af3fa7ac 100644 --- a/_posts/2015-05-01-graphql-introduction.md +++ b/_posts/2015-05-01-graphql-introduction.md @@ -69,7 +69,7 @@ Obviously GraphQL is not the first system to manage client-server interactions. ### REST -REST an acronym for Representational State Transfer, which is an architectural style rather than a formal protocol. There is actually much debate about what exactly REST is and is not. We wish to avoid such debates. We are interested in the typical attributes of systems that *self-identify* as REST, rather than systems which are formally REST. +REST, an acronym for Representational State Transfer, is an architectural style rather than a formal protocol. There is actually much debate about what exactly REST is and is not. We wish to avoid such debates. We are interested in the typical attributes of systems that *self-identify* as REST, rather than systems which are formally REST. Objects in a typical REST system are addressable by URI and interacted with using verbs in the HTTP protocol. An HTTP GET to a particular URI fetches an object and returns a server-specified set of fields. An HTTP PUT edits an object; an HTTP DELETE deletes an object; and so on.