Talk:Representational state transfer

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Friendlier opening paragraph[edit]

I made a start to try to introduce the topic in a less techno-dense way. It probably could say more but unless I'm telling an actual lie, please don't revert or change it back to "incredibly technical". Ordinary people (eg scrum masters) might like to know what REST is. Aelfgifu (talk) 10:38, 24 August 2016 (UTC)

The opening paragraph starts with "... representational state transfer (REST) or RESTful is an architectural style ...". RESTful should be removed, in my opinion. "REST" and "RESTful" are not the same, the same way "art" and "artful" are not the same. At the end of the first section, RESTful is correctly defined: "To the extent that systems conform to the constraints of REST they can be called RESTful". So, again in my opinion, RESTful should be dropped from the opening line. I would have done it myself, but since I see there are people more involved than me in looking after the page, I just mention this here. (talk) 09:44, 29 September 2016 (UTC)
What is the difference between REST and RESTful? There is a slight grammatical difference but the two terms are used interchangeably within the software field. Accordingly an encyclopaedia article should list both in the lead. Andy Dingley (talk) 09:50, 29 September 2016 (UTC)
Nigelj fixed it. Now it reads "... RESTful web services is an architectural style ...", which is grammatically correct. It might be a technical subject, but grammar is always important. Imagine saying: "Your RESTful is not standards compliant". What does it mean? Your restful API? Your restful programming? Your restful service? RESTful is an adjective. (talk) 13:54, 29 September 2016 (UTC)

Reading the first paragraph, especially the first sentence, has real semantic problems: only by clicking the cross reference could I begin to grasp what might have been intended. The words "architectural style" are particularly at issue, as architectural style is commonly related to the original meaning of architecture as a description of a building looks and is constructed. The use of architecture for software is metaphorical and it is unclear what a style means in that context. For instance, for the word style to be meaningful in this sentence other software architectural styles should exist, and be known, and should be referenced in the paragraph to provide context. Similar semantic which-ups exist in the remainder of the paragraph where cross-references are used in a sentence construct that does not really make clear how the linked concept relates to REST. I'll do an edit and hopefully we can get that tag removed. — Preceding unsigned comment added by EduardKarelEtc (talkcontribs) 13:07, 10 January 2021 (UTC)

Article could really use more of an example early on and less of a giant wall of text[edit]

I was explaining to an intern what REST was and I thought I'd send them this but holy crap this wouldn't be helpful. Early on in the article it should show an example where a get or post is called and some JSON is passed. Yes I know that technically it doesn't have to be and bla bla bla bla but in "basically what is it and how are people using the term" REALLY early on (like most other comp sci articles) it should have this. I'd add it myself but I've learned that articles with long talk pages are best not edited because some opinionated person will start an edit war...Just consider "would this actually help explain this" if someone asked "What is REST?" without already knowing it basically...and "what would make it actually work for that?" and I think you'll see what I mean Reboot (talk) 15:20, 22 May 2017 (UTC)

Are you thinking of AJAX? --Nigelj (talk) 14:52, 23 May 2017 (UTC)
Apparently you talking to your intern about Web APIs and for some reason you were compelled to inject the term REST. Pasado (talk) 23:23, 29 May 2017 (UTC)


Since the e in REST does not represent a word, should it be written ReST? — Preceding unsigned comment added by (talk) 13:57, 8 May 2020 (UTC)

No, that's not the spelling in use. 2A00:23C5:FE0C:2100:D74:7CAF:3D41:2C85 (talk) 10:25, 25 December 2020 (UTC)

First sentence should not include HTTP in the definition.[edit]

"Representational state transfer (REST) is a software architectural style which uses a subset of HTTP."

Is the use of HTTP a necessary condition of a RESTful architecture? From Fielding's dissertation: "For example, the Web's primary transfer protocol is HTTP, but the architecture also includes seamless access to resources that originate on pre-existing network servers, including FTP [107], Gopher [7], and WAIS [36]. "

In practice, REST might all but imply HTTP, but the communication protocol is just an implementation detail with respect to the architectural style, no? Should this first sentence be rewritten? I'm not expert enough to propose an alternative, but this seems problematic.

will (talk) 14:44, 4 June 2021 (UTC)

Add other HTTP methods[edit]

Should other HTTP request methods be included in the Semantics of HTTP Methods section? PATCH seems important, for example, when updating a target with limited representation, as opposed to creating/replacing with PUT.

Owenjpgallagher (talk) 17:59, 17 September 2021 (UTC)