Nathan Vander Wilt

Thanks, that's helpful for that side of things! On the other side, I'm realizing I need to revisit the API for this and #33 though — the whole point of...

@legomind Not really, I'm hoping to polish up and release the `upcoming` branch soon but I'm not sure if this will make the cut. There's still a lot of unknowns...

Wanted to write up some recent (design) progress I've made on this recently, especially a potential breakthrough I had the other day on this. First off, I think at least...

Oh, I didn't call this out, but worth expounding on here: Another thing that made me squeamish about promises is that fermata now returns both data and metadata as _two_...

@ricxsar No, I haven't gotten much feedback lately and don't use Promises enough myself to judge how useful this would be.

Update: we need Promise support for `async`/`await`. See also #65.

`await` does work with other objects, since ECMAScript 2017 section 25.5.5.3 [defines AsyncFunctionAwait](https://www.ecma-international.org/ecma-262/8.0/index.html#sec-async-functions-abstract-operations-async-function-await) ± in terms of `Promise.resolve` on await's value, which in turn works on any then-able object: ```...

While I like the idea of moving data "collection" to a plugin, I think this would sometimes be a per-request thing. This is probably an open question for the design:...

So here's another angle: the browser doesn't really support "streams" /per se/ and in node.js it's not too unreasonable to just use `http.request` directly if you're at raw-ish streams level...

Still leaning towards a simple helper, or merely documenting the `hh.get(url())` pattern. This keeps our design focused on its two fortes: building URLs, transporting objects to/from them. However, doesn't `url.post(stream,...