General concept is that when a function (or method) has multi return values one being an error, error should be checked first and only proceed if the error is nil. Functions should return zero values for other (non-error) values if there is an error. If the function behaves differently, it should be documented. http.Get() does … Read more
If you know how many Ajax-Calls you have, simply use $.when() $.when(doAjax(‘a’),doAjax(‘b’),doAjax(‘c’),doAjax(‘d’)) .then(function(result_a,result_b,result_c,result_d) { console.log(“Result from query a: ” + result_a); console.log(“Result from query b: ” + result_b); console.log(“Result from query c: ” + result_c); console.log(“Result from query d: ” + result_d); }); If you don’t know how many ajax-calls you will have, you can … Read more
Don’t use a queue and that boolean flag, just have one variable storing a promise representing all uploads. Also, your upload function should not take a Deferred object to resolve as an argument, but simply return a new promise. Then the addAnUpload becomes as simple as var allUploads = $q.when(); // init with resolved promise … Read more
There are many ways to write this kind of thing. A flexible approach is separate “actions” from “sequence”, allowing : functions a, b, c to initiate an asynchronous (ajax) action, with no knowledge of how they are to be sequenced a, b, c to be reusable, as part of one or more sequences or individually, … Read more
Just use a thread. import threading t = threading.Thread(target=long_process, args=args, kwargs=kwargs) t.setDaemon(True) t.start() return HttpResponse() See this question for more details: Can Django do multi-thread works?
Q promises can be resolved with only one argument – a promise stands for one single value, not for a collection of them. Put them in an array explicitly if you need multiple values. For the multiple-parameter-callbacks, you can use .spread().
Same idea, but you may find it slightly classier or more compact: funcs.reduce((prev, cur) => prev.then(cur), starting_promise); If you have no specific starting_promise you want to use, just use Promise.resolve().
Since routes are defined on a provider level, normally new routes can only be defined in the configuration block. The trouble is that in the configuration block all the vital services are still undefined (most notably $http). So, on the surface it looks like w can’t define routes dynamically. Now, it turns out that in … Read more
Am I using the wrong approach for deferreds and promises? Yes. In the asynchronous callback you should not access promises, but only the callback arguments. The return promise of $.when does resolve with an array of the .resolve() parameters for each of the promises in the array – you can loop over the arguments object … Read more
With a custom object function DeferredAjax(opts) { this.options=opts; this.deferred=$.Deferred(); this.country=opts.country; } DeferredAjax.prototype.invoke=function() { var self=this, data={country:self.country}; console.log(“Making request for [” + self.country + “]”); return $.ajax({ type: “GET”, url: “wait.php”, data: data, dataType: “JSON”, success: function(){ console.log(“Successful request for [” + self.country + “]”); self.deferred.resolve(); } }); }; DeferredAjax.prototype.promise=function() { return this.deferred.promise(); }; var countries … Read more