fermata
fermata copied to clipboard
natevw
Succinct native REST client, for client-side web apps and node.js. Turns URLs into (optionally: magic!) JavaScript objects.
If CouchDB gets upset, it may simply close the incoming pipe as it sends a repsonse. Rather than getting the response as an error, fermata returns only: ``` { Error:...
Seeing a situation where an early server response can trigger error callback, and then (if the posted stream is ended) an EPIPE on passed stream can _also_ trigger an error...
Since npm takes care of all the file mess, we might as well keep the main `fermata.js` primarily focused on browser, with only stubs to require the node.js–specific stuff. We're...
Because of https://github.com/rogerwang/node-webkit/issues/1588 and in a hurry I just made a node-webkit branch that changes the `window` check for an `exports` one. I liked the former better, and don't want...
While keeping authorization "simple" by requiring it integrated into the base url has a little advantage, it is contrary to one of Fermata's core principles: I should not have to...
Consider this code: ``` queue() .defer(api.db.doc1.get) .defer(api.calculator.post, "sin(2.71828182846)") .await(function (e, thing1, thing2) { console.log(e, thing1.number + thing2.result); }); ``` In this case, the queue code must [.apply](https://github.com/mbostock/queue/blob/master/queue.js#L70) our arguments to...
http://requirejs.org/docs/whyamd.html, some sample patterns here: https://github.com/umdjs/umd
Hi folks, The module is great but I found a little issue with endpoints terminating by a slash. **Not works**: ``` javascript site.v1.resource["1"].get(console.log) // Fermata dislikes the 501 redirection ```...
Right now we get fancy with pretty-casing the headers. It's really nice to see happy "Date", "Content-Type", "Cache-Control", etc. but we'd almost have to special case ones like "Www-Authenticate". Moreso,...