Review PATCH/409 - Githubissues

for-GET / http-decision-diagram

An activity diagram to describe the resolution of HTTP response status codes, given various headers.

https://github.com/for-GET/http-decision-diagram/blob/master/doc/2013-06-10-http-hell-no.md

Apache License 2.0

3.61k stars 196 forks source link

Review PATCH/409 #36

Closed andreineculau closed 9 years ago

andreineculau commented 10 years ago

Food for thought:

leave the catch-all for non RFC2616 methods
add conflict/409 check for PATCH just like for PUT
extract the create/process block into a "standalone" FSM

Ref: https://github.com/for-GET/http-decision-diagram/issues/35#issuecomment-28976781

bethesque commented 9 years ago

Is this project being maintained? What's the status of PATCH support for the next version of the diagram?

andreineculau commented 9 years ago

@bethesque maintained yes, but I haven't put energy into actively developing it recently (last year).

FWIW, I don't think PATCH needed "more" support, but I have updated the diagram to make it explicit that 1) PATCH should handle 409 as well 2) requests can return "resource content" (i.e. content that would be returned to a GET request) requiring Content-Location header

And I think that's all. I will close the issue, but please ping me if you have questions or if it doesn't sound just right.

bethesque commented 9 years ago

So, PATCH would follow is_method_process => true when the resource exists, and is_method_create => true when the resource does not exist?

andreineculau commented 9 years ago

yup

On Sun, Oct 12, 2014 at 10:21 PM, Beth notifications@github.com wrote:

So, PATCH would follow is_method_process => true when the resource exists, and is_method_create => true when the resource does not exist?

— Reply to this email directly or view it on GitHub https://github.com/for-GET/http-decision-diagram/issues/36#issuecomment-58820918 .

andreineculau.com http://www.andreineculau.com