Julian Gruber
Julian Gruber
There probably is more work necessary to make this run in browsers, for example this relies on `async_hook` and `process` events currently. @thlorenz asked about browser compatibility too. I think...
@aduh95 how do you feel about this? What about we package all of the above in a new module, for `node-core-*` projects to consume?
using promises is safe and sound at the moment, and since they will be able to be `await`ed that sounds like a no brainer to me
+1 node https support is great for adoption
Thank you for asking :) I think the text is fine!
It's like with node and core modules. The http module could live on npm too, but it's so core-y and heavily used that the core is the place it belongs....
we have `levelDOWN`, `levelUp` and recently `level` too! This means `levelUp` needn't necessarily know about sublevel, it can all be in `level`.
I already experimented with connect style middleware in leveled, see: https://github.com/juliangruber/node-leveled/tree/middleware#todo https://github.com/juliangruber/node-leveled/blob/middleware/lib/middleware/queue.js https://github.com/juliangruber/node-leveled/blob/middleware/index.js#L18
it basically has ``` js var req= { key: key, val: val, method: method /* put, del, etc. */ } var res = { end: function (err, data) { /*...
how would you change the key for all operations? ``` js exports.put = function (key, value, next) { key = 'foo'; // now you reassigned `key` instead of changing it...