)]}'
{"guidelines/http.rst":[{"author":{"_account_id":12321,"name":"Ryan Brown","email":"rybrown@redhat.com","username":"ryansb"},"change_message_id":"8e1bd0b9511588e149d26c05bf780418e5cca461","unresolved":false,"context_lines":[{"line_number":150,"context_line":""},{"line_number":151,"context_line":"This looks close to a CRUD mapping, but it\u0027s important to realize the"},{"line_number":152,"context_line":"defining characteristic of POST isn\u0027t that it creates items, but that"},{"line_number":153,"context_line":"you POST to a URI that\u0027s different than the resource you get"},{"line_number":154,"context_line":"back. POST is therefor also appropriate for bulk operations like"},{"line_number":155,"context_line":"multiple update, or triggering some arbitrary other actions beyond"},{"line_number":156,"context_line":"resource creation (i.e. reboot a server)."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_5a32875f","line":153,"updated":"2015-06-23 19:43:35.000000000","message":"For example, say you\u0027re modifying the resource of type foo with the ID 123. You would use \"PUT /foo/123\" and the modification would occur. For POST, you could POST the new data directly to \"/foo\" and you would recieve back the new URI, say \"/foo/1111\".","commit_id":"e706a6fd8289c0428b94954eff0e40251e247eb7"},{"author":{"_account_id":6062,"name":"jichenjc","email":"jichenjc@cn.ibm.com","username":"jichenjc"},"change_message_id":"eb75a4a57fbe93d85b49e6276fb0c605e4a993df","unresolved":false,"context_lines":[{"line_number":150,"context_line":""},{"line_number":151,"context_line":"This looks close to a CRUD mapping, but it\u0027s important to realize the"},{"line_number":152,"context_line":"defining characteristic of POST isn\u0027t that it creates items, but that"},{"line_number":153,"context_line":"you POST to a URI that\u0027s different than the resource you get"},{"line_number":154,"context_line":"back. POST is therefor also appropriate for bulk operations like"},{"line_number":155,"context_line":"multiple update, or triggering some arbitrary other actions beyond"},{"line_number":156,"context_line":"resource creation (i.e. reboot a server)."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1af86dd1_70bb82c5","line":153,"updated":"2015-06-12 16:41:57.000000000","message":"sorry, do you mean the resource get back is different to URI?\ncan you help me in understand it? thanks","commit_id":"e706a6fd8289c0428b94954eff0e40251e247eb7"},{"author":{"_account_id":1063,"name":"Ed Leafe","email":"ed@leafe.com","username":"ed-leafe"},"change_message_id":"536ab6326be4bac7b9611f2f0d991d1b7f8e8fce","unresolved":false,"context_lines":[{"line_number":150,"context_line":""},{"line_number":151,"context_line":"This looks close to a CRUD mapping, but it\u0027s important to realize the"},{"line_number":152,"context_line":"defining characteristic of POST isn\u0027t that it creates items, but that"},{"line_number":153,"context_line":"you POST to a URI that\u0027s different than the resource you get"},{"line_number":154,"context_line":"back. POST is therefor also appropriate for bulk operations like"},{"line_number":155,"context_line":"multiple update, or triggering some arbitrary other actions beyond"},{"line_number":156,"context_line":"resource creation (i.e. reboot a server)."}],"source_content_type":"text/x-rst","patch_set":1,"id":"ba3cc151_3238ea9f","line":153,"in_reply_to":"fa32b979_5a32875f","updated":"2015-07-08 20:17:50.000000000","message":"Small refinement: PUT can also create, but you must specify the full resource, including any ID. Swift does this when creating containers and objects.","commit_id":"e706a6fd8289c0428b94954eff0e40251e247eb7"},{"author":{"_account_id":177,"name":"Alex Meade","email":"mr.alex.meade@gmail.com","username":"alex-meade"},"change_message_id":"6383066c05b74b6846871e3c602f1c5081b73416","unresolved":false,"context_lines":[{"line_number":151,"context_line":"This looks close to a CRUD mapping, but it\u0027s important to realize the"},{"line_number":152,"context_line":"defining characteristic of POST isn\u0027t that it creates items, but that"},{"line_number":153,"context_line":"you POST to a URI that\u0027s different than the resource you get"},{"line_number":154,"context_line":"back. POST is therefor also appropriate for bulk operations like"},{"line_number":155,"context_line":"multiple update, or triggering some arbitrary other actions beyond"},{"line_number":156,"context_line":"resource creation (i.e. reboot a server)."},{"line_number":157,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"ba3cc151_9b8947cd","line":154,"updated":"2015-07-06 21:25:29.000000000","message":"s/therefor/therefore","commit_id":"e706a6fd8289c0428b94954eff0e40251e247eb7"},{"author":{"_account_id":12321,"name":"Ryan Brown","email":"rybrown@redhat.com","username":"ryansb"},"change_message_id":"12ee65495cbc7611c4a1fa1bc8cc986597aa0408","unresolved":false,"context_lines":[{"line_number":151,"context_line":"This looks close to a CRUD mapping, but it\u0027s important to realize the"},{"line_number":152,"context_line":"defining characteristic of POST isn\u0027t that it creates items, but that"},{"line_number":153,"context_line":"you POST to a URI that\u0027s different than the resource you get"},{"line_number":154,"context_line":"back. POST is therefor also appropriate for bulk operations like"},{"line_number":155,"context_line":"multiple update, or triggering some arbitrary other actions beyond"},{"line_number":156,"context_line":"resource creation (i.e. reboot a server)."},{"line_number":157,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"ba3cc151_f5dd9e14","line":154,"in_reply_to":"ba3cc151_9b8947cd","updated":"2015-07-08 14:58:10.000000000","message":"Actually therefor and therefore are both acceptable spellings, with therefor being preferred for legalistic prose, while therefore is used in less formal settings. IMO, either is fine for this type of guideline.","commit_id":"e706a6fd8289c0428b94954eff0e40251e247eb7"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"9c3f90b6be31384b7927a42ccc298a6a1f33c1e1","unresolved":false,"context_lines":[{"line_number":153,"context_line":"you POST to a URI that\u0027s different than the resource you get"},{"line_number":154,"context_line":"back. POST is therefor also appropriate for bulk operations like"},{"line_number":155,"context_line":"multiple update, or triggering some arbitrary other actions beyond"},{"line_number":156,"context_line":"resource creation (i.e. reboot a server)."},{"line_number":157,"context_line":""},{"line_number":158,"context_line":"**TODO**: HEAD is weird in a bunch of our wsgi frameworks and you"},{"line_number":159,"context_line":"don\u0027t have access to it. Figure out if there is anything useful"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_3bc6a29a","line":156,"updated":"2015-06-23 22:34:03.000000000","message":"This clarification is important and it is exposed in a very clear way.","commit_id":"e706a6fd8289c0428b94954eff0e40251e247eb7"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"9c3f90b6be31384b7927a42ccc298a6a1f33c1e1","unresolved":false,"context_lines":[{"line_number":157,"context_line":""},{"line_number":158,"context_line":"**TODO**: HEAD is weird in a bunch of our wsgi frameworks and you"},{"line_number":159,"context_line":"don\u0027t have access to it. Figure out if there is anything useful"},{"line_number":160,"context_line":"there."},{"line_number":161,"context_line":""},{"line_number":162,"context_line":"**TODO**: Provide guidance on what HTTP methods (PUT/POST/PATCH/DELETE, etc)"},{"line_number":163,"context_line":"should always be supported, and which should be preferred."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_bb0632cc","line":160,"updated":"2015-06-23 22:34:03.000000000","message":"What you write here is correct, but that does not detract anything from the semantics of HEAD, which are those reported in the table you are introducing here.\n\nAre suggesting to replace at some point a todo with a section on caveats concerning specific WSGI frameworks and HEAD? That would work for me but I\u0027m not sure API guidelines should go into this kind of details. Frameworks evolve, die, and are born. the guideline stays (well kind of)","commit_id":"e706a6fd8289c0428b94954eff0e40251e247eb7"},{"author":{"_account_id":1063,"name":"Ed Leafe","email":"ed@leafe.com","username":"ed-leafe"},"change_message_id":"16ed4b0c8a5d799340bc79ee3ea1864b0303752b","unresolved":false,"context_lines":[{"line_number":157,"context_line":""},{"line_number":158,"context_line":"**TODO**: HEAD is weird in a bunch of our wsgi frameworks and you"},{"line_number":159,"context_line":"don\u0027t have access to it. Figure out if there is anything useful"},{"line_number":160,"context_line":"there."},{"line_number":161,"context_line":""},{"line_number":162,"context_line":"**TODO**: Provide guidance on what HTTP methods (PUT/POST/PATCH/DELETE, etc)"},{"line_number":163,"context_line":"should always be supported, and which should be preferred."}],"source_content_type":"text/x-rst","patch_set":1,"id":"da20952f_a51c6914","line":160,"in_reply_to":"fa32b979_bb0632cc","updated":"2015-09-01 16:13:32.000000000","message":"Agree that this isn\u0027t necessary. These docs represent a consistent approach to APIs, and not workarounds for specific frameworks.","commit_id":"e706a6fd8289c0428b94954eff0e40251e247eb7"}]}