261 karma · joined March 4, 2013
http://ysoftware.se http://andreineculau.com
A good read: https://www.safaribooksonline.com/library/view/restful-web-s...
https://github.com/for-GET/know-your-http-well/blob/master/s...
* an old PoC in NodeJS exists that reads the states/transitions from a JSON file and calls the correct callbacks in the correct order. Implement the callbacks (semantics) and you're done.
Disclaimer: I'm the author.
Source: https://github.com/blogandreineculaucom/blogandreineculaucom...
Theme live at: http://blog.andreineculau.com (blog content not so much alive)
Even if I kept two email addresses, resetting a password should have more steps than just "click this link once" in any of those inboxes.
Build on top, reuse, don't copy-paste!
which coupled with a browser search plugin http://mycroftproject.com/search-engines.html?name=bin.hyper... can brings specifications to the tip of your... "bin+tab" :)
Opensourced at https://github.com/hyperrest/bin
2) most job ads don't know what they are after, but they know they are after a "ninja"
3) no, not all job ads are like this - http://webcache.googleusercontent.com/search?q=cache:86X5cn0...
4) I would not require anyone to know HTTP by heart, but to have understood deeply whatever I-D (s)he has read (and remembers) on HTTP
- I value software that keeps to the spec, because it's the spec that I (as a dev or non-dev) refer to. You never hear "NodeJS has HTTPish module", nor do you read documentation of that module's concepts and behaviour. Those are defined in the spec, and the __fill_in_with_any_language__ HTTP module just implements those definitions.
- Optimizations, simplifications, corrections should be done in the spec, whenever the you find them at implementation-time.
But until now there has not been ONE HTTP server that grasps and handles the HTTP specs in their whole. So then, I find it hilarious to read that about optimizations when neither of us have the whole picture.
That said, I don't think it's Node.js to blame here (albeit they do have weird views of standards: https://github.com/joyent/node/issues/4850) but HTTP itself because the spec's abstraction levels have been far away from the implementations' reach. HTTPs concepts are gorgeous but they are worth nil if implementation is "hard" and never done properly.
Longer story at: http://andreineculau.github.io/hyperrest/2013-06-10-http-hel...
If you like KATT/Apiary/HTTP mockeries, keep an eye on https://github.com/andreineculau/hyperrest-bin and https://github.com/klarna/katt