sharpetronics/hypermedia-systems
1
0
Fork 0
mirror of https://github.com/bigskysoftware/hypermedia-systems.git synced 2025-12-06 00:02:36 -05:00
Code Issues Projects Releases Wiki Activity

Update CH02_ComponentsOfAHypermediaSystem.adoc

Browse Source 
Change RCF to RFC in 2 places
This commit is contained in:
B. Burt 2023-03-11 23:31:51 -08:00 committed by GitHub
parent 8a19791c26
commit 0ed6ddaa67
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
book/CH02_ComponentsOfAHypermediaSystem.adoc
View File

@ -176,9 +176,9 @@ These methods _roughly_ line up with the "`Create/Read/Update/Delete`" or CRUD p
.Put vs. Post
****
While HTTP Actions correspond roughly to CRUD, they are not the same. The technical specfications for these methods make no such connection, and are often somewhat difficult to read. Here, for example, is the documentation
on the distinction between a `POST` and a `PUT` from https://www.rfc-editor.org/rfc/rfc2616[RCF-2616].
on the distinction between a `POST` and a `PUT` from https://www.rfc-editor.org/rfc/rfc2616[RFC-2616].
[quote, RCF-2616, https://www.rfc-editor.org/rfc/rfc2616#section-9.6]
[quote, RFC-2616, https://www.rfc-editor.org/rfc/rfc2616#section-9.6]
____
The target resource in a POST request is intended to handle the enclosed representation according to the
resource's own semantics, whereas the enclosed representation in a PUT request is defined as replacing the state of the