If you're looking for a quick solution to your inquiry, the answer lies within using a Promise.
Promises are a design pattern that may soon become integrated into ECMA-6. Currently, they can be implemented through custom code or libraries like Kris Kowal's q (referenced below).
The concept is rather straightforward. The objective is to encapsulate an asynchronously-executing method or function in order to maintain its scope and then act upon its return value. In most scenarios, this process is referred to as a "then statement."
Here's a basic example:
var theEventualResults;
goGetMeSomething().then(function(results) {
// Store the results in the appropriate scope
theEventualResults = results;
});
The premise here is that goGetMeSomething() returns a "Promise Object" with a then method that executes once the initial function completes successfully. There are also ways to handle failures, such as error catching or interpreting failure response codes from requests.
A depiction of handling failure:
var theEventualResults;
goGetMeSomething().then(function(results) {
// Store the results in the working scope
theEventualResults = results;
}).error(function(reason) {
// Deal with any potential failures
});
I recommend delving into research on Promises and their varied implementations in different libraries to enhance your understanding. This exploration will aid you in determining the ideal approach for your specific application.
In conclusion of your inquiries:
- How can one identify and manage this situation in both successful and erroneous responses?
- A Promise pattern would likely prove most beneficial.
- Can this matter be addressed from a high-level architectural viewpoint, or will solutions always tie back to JavaScript frameworks or application types?
- Solutions can be independently applied in JavaScript without any framework dependency. However, if utilizing a framework, it might already offer a Promise mechanism. It's usually advisable to utilize what the framework provides instead of seeking alternatives. Take AngularJS, for instance, as exemplified by Alex C.
- Regarding web applications, is it recommended to block input during server-side processing?
- This topic extends beyond scope here. I suggest raising this as a separate question.
Below are some library references:
I'm not advocating for the use of any particular library. Your discovery journey should guide you in making that decision. Hopefully, this breakdown aids in recognizing the pattern, empowering you to make an informed choice.
javascriptqasynchronouswinjsrsvppromise