http-decision-diagram
http-decision-diagram copied to clipboard
client & cache diagram
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/
http://course.wilkes.edu/engineer/discuss/msgReader$3?mode=topic
http://bizcoder.com/caching-is-hard-draw-me-a-picture
http://www.silota.com/site-search-blog/must-have-api-client/
http://www.bizcoder.com/the-insanity-of-the-vary-header
I agree that a client http decision diagram would be helpful and maybe a reference implementation in JavaScript using xstate?
@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.