{"id":59895,"date":"2018-05-03T16:01:10","date_gmt":"2018-05-03T10:31:10","guid":{"rendered":"https:\/\/www.vskills.in\/certification\/tutorial\/?p=59895"},"modified":"2024-04-12T14:20:50","modified_gmt":"2024-04-12T08:50:50","slug":"angular-promises","status":"publish","type":"page","link":"https:\/\/www.vskills.in\/certification\/tutorial\/angular-promises\/","title":{"rendered":"Angular Promises"},"content":{"rendered":"

Angular Promises<\/h1>\n

Promises are a pattern that helps with one particular kind of asynchronous programming: a function (or method) that returns a single result asynchronously. One popular way of receiving such a result is via a callback (\u201ccallbacks as continuations\u201d):<\/p>\n

asyncFunction(arg1, arg2,<\/p>\n

result => {<\/p>\n

console.log(result);<\/p>\n

});<\/p>\n

Promises are not actually complicated, they’re objects that contain a reference to functions to call when something fails or succeeds.<\/p>\n

Under the hood, AngularJS actually wires up a promise for an HTTP request in a way a bit like this:<\/p>\n

var request = new XMLHttpRequest();
\nrequest.addEventListener(“load”, function() {
\n\/\/ complete the promise
\n}, false);
\nrequest.addEventListener(“error”, function() {
\n\/\/ fail the promise
\n}, false);
\nrequest.open(“GET”, “\/api\/my\/name”, true);
\nrequest.send();<\/p>\n

this is pseudo-code, but the idea is that its the browser that calls us back, via the event listeners, then AngularJS can just call the appropriate method on the promise.<\/p>\n

Now in AngularJS, the promises are created with the $q service (we’ll see exactly how to do this shortly), but why $q?<\/p>\n

The reason the service is named $q is that AngularJS’ promise implementation is based on Kris Kowal’s promise mechanism, which is called ‘Q’. You can see the library at github.com\/kristkowal\/q.<\/p>\n

This was a deliberate decision, as the Q library is widely used and well understood by the community. We’re going to see a little bit later what the future of promises is in AngularJS and actually in ECMAScript 6.
\nA Real World Example<\/p>\n

In this example, we’ll create a service that gets the user’s name, just like in our examples. However, to make it interesting, we’ll set our service up so that the first time we get the name from the server, and then afterwards we’ll return a cached copy.<\/p>\n

This means we’ll have to build our code to deal with the asynchronous case (the first one) and the more trivial synchronous case (getting the name from the cache).<\/p>\n

Let’s look at a pure asynchronous implementation.<\/p>\n

app.factory(‘NameService’, function($http, $q) {<\/p>\n

\/\/ Create a class that represents our name service.
\nfunction NameService() {<\/p>\n

var self = this;<\/p>\n

\/\/ getName returns a promise which when
\n\/\/ fulfilled returns the name.
\nself.getName = function() {
\nreturn $http.get(‘\/api\/my\/name’);
\n};
\n}<\/p>\n

return new NameService();
\n});<\/p>\n

Now let’s update our service so that we hit the server only if we haven’t already cached the name. I’ll build the service blow by blow, then we can see a fiddle of it working.<\/p>\n

app.factory(‘NameService’, function($http, $q) {<\/p>\n

\/\/ Create a class that represents our name service.
\nfunction NameService() {<\/p>\n

var self = this;<\/p>\n

\/\/ Initially the name is unknown….
\nself.name = null;<\/p>\n

so first we create a service which is in the form of a class. It has a name field which is initially null.<\/p>\n

self.getName = function() {
\n\/\/ Create a deferred operation.
\nvar deferred = $q.defer();<\/p>\n

Now in the getName function we start by creating a deferred object, using the $q service. This object contains the promise we’ll return, and has some helper functions to let us build the promise.<\/p>\n

We create a deferred object because whether we use ajax or not, we want the consumer to use the promise – even if we can return straightaway in some circumstances (when we have the name) we can’t in all – so the caller must always expect a promise.<\/p>\n

if(self.name !== null) {
\ndeferred.resolve(self.name + ” (from Cache!)”);
\n}<\/p>\n

If we already have the name, we can just resolve the deferred object immediately – this is the easy case. I’ve added ‘from cache’ to the name so we can see when it comes from the cache compared to the server.<\/p>\n

Finally, we can handle the case if we don’t already have the name:<\/p>\n

else {
\n\/\/ Get the name from the server.
\n$http.get(‘\/api\/my\/name\/’)
\n.success(function(name) {
\nself.name = name;
\ndeferred.resolve(name + ” (from Server!)”);
\n})
\n.error(function(response) {
\ndeferred.reject(response);
\n});
\n}<\/p>\n

So if we get success from the server, we can resolve the promise. Otherwise, we reject it, which means failure.<\/p>\n

IT Professionals, Web Developers, web programmers, IT students can Apply for the certification course and get ahead.<\/strong><\/p>\n

\"\"<\/a><\/p>\n