search

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

client & cache diagram #14

Open andreineculau opened 11 years ago

andreineculau commented 11 years ago

it is not only the server that can benefit from an FSM to decide the HTTP response flow, but also the client and the cache proxy (a version is already in master branch based on @darrelmiller's versions)

trigger: http://blog.safaribooksonline.com/2013/05/31/rest-from-a-client-perspective/

andreineculau commented 10 years ago

http://course.wilkes.edu/engineer/discuss/msgReader$3?mode=topic

andreineculau commented 10 years ago

http://bizcoder.com/caching-is-hard-draw-me-a-picture

andreineculau commented 10 years ago

http://www.silota.com/site-search-blog/must-have-api-client/

andreineculau commented 10 years ago

http://www.bizcoder.com/the-insanity-of-the-vary-header

pke commented 3 years ago

I agree that a client http decision diagram would be helpful and maybe a reference implementation in JavaScript using xstate?

andreineculau commented 3 years ago

@pke thanks for your interest and your comment! Had no idea about https://github.com/davidkpiano/xstate . I have used https://github.com/ifandelse/machina.js/ 7 years ago. And it looks rather easy to parse cosmogol into xstate.