I'm having a bit of an issue with asynchronous fetch operation. Fetch operation starts on componentWillMount() and if causes issue if the user navigates back before a response is generated. I need a workaround to not update state with data response ...
Join discussionI am currently developing a new IoT-project and we decided to program it in rust since part of the embedded architecture can run the same code as the server side. mainly the COAP utilizing the 6lowpan for meshing and a classic NFC communication. I h...
MMarco commentedWell, in Node.js or in Clojure... I ran into a problem — all of the requests are relying on a task on the server. So they have to wait until the task is finished. I got one solution from my friend — use promise to wrap the task and let others use yie...
NMDenny and 1 more commentedI came across this scenario while coding recently. I have an async function like this. exports.dummy = function (req, res, next) { async.waterfall([ function (cb) { /.../ cb(); }, function (cb1) { if (/*something*/) { ...
SSandeep commentedI'm a sucker for trying out new ideas in JS, and have fully jumped on board the ES201X train. I have read about CSP and coroutines in the past (specifically in relation to https://github.com/getify/asynquence) but never really had a go, the syntax wa...
NDenny commented