Sunday, April 2, 2017

Evolution of AJAX World

If you have started you carrier around 7-10 years back as web developer then probably you have experienced the evaluation practically.

Because of huge advantage of AJAX, more or less 70-80 % of modern web application has adapted this technology. The new style of AJAX implementation came in market so quickly that it’s sometime hard to remember what things were before that?

Anyway, Long ago, Netscape added a feature in browser called live script which was capable to give flavor of offline processing like form validation in client side and bit more. Slowly Live script became JavaScript with more functionality and flexibility.

The inception of DynamicHTML has started in development world, slowly XML gain its popularity in AJAX world when Microsoft added a small function in IE5 to perform XMLHttpRequest call to server.

The classic AJAX using XMLHttpRequest

This is classic style to make AJAX call using vanilla JavaScript. If you worked in very old ASP, JSP or PHP application, probably you are familiar with this style of AJAX call.

var xhttp = new XMLHttpRequest();
xhttp.onreadystatechange = function() {
    if (this.readyState == 4 && this.status == 200) {
       // Typical action to be performed when the document is ready:
       document.getElementById("demo").innerHTML = xhttp.responseText;
};"GET", "yourfilename.extension", true);

Oh, did I miss something? Yes, we need to detect browser prior to AJAX call, Just to make sure we are using proper XMLHttpRequest object. Yes, XMLHttpRequest object is browser specific.

JQuery changed the whole game

Then JQuery came in market, it played major role to change face of client side app development.  It combine and packed the above code into few lines and introduce the concept of Callback.

$.ajax({url: "", success: function(result){
        //enjoy with result variable

And that’s all, simple, compact, no code smell and maintainable. Now, in mean time other library too started wrapping classic XMLHttpRequest request using very similar syntax.

So, as a result the concept of callback has introduced in development world. The moto of callback is, call me once you have prepared the result, or call error in mess!.

Let’s return promise rather than actual result

People started to realize that, as it is asynchronous call, it should return something by which we can take decision. Let’s give some example. The below code is based on promise and then callback function.

requestSomeData(" ") // returns a promise for the response

    .then(function(response){ // ‘then’ is used to provide a promise handler
    return JSON.parse(response.body); // parse the body
   }) // returns a promise for the parsed body

    return data.something; // get the price

   }) // returns a promise for the price

    .then(function(price){ // print out the price when it is fulfilled

        //do something with the data


We can consider this as fully asynchronous execution plan, even if my JSON.parse() take huge time, the execution flow will not hang the thread because I have attached then callback to ensure that someone will take care once parse completed.

Angular and Other library utilize it best

Angular 1.X introduced a way to sync all asyn call using “$q” service. This is huge power to developer to process more than one asynchronous call and print consolidated result.

Want to have more control on AJAX call? Use Observable.

RxJs introduced the concept called Observable to have more grip on AJAX call. Let’s think that we need to cancel an AJAX call in middle. Assume, the situation where need to handle multiple AJAX call. Observable is preferred than promise here.

So, an observable is like a stream and allow to pass zero or more events where the callback is called for each event. The Observable covers more including promise.
For more info, please check Observable in Angular2


Saturday, April 1, 2017

Learning Angular2 ? Here you map yourself !

What is new in angular2?
               Let's see, do I really need to learn!

Advantages of angular2
               If there, industry will adapt quickly and I have to spend some amount of time to learn. Good advantages are bad news for "coder by incident" Engineer :)

Does typescript really need in angular2?
               It could be gossip, let's check reality. Oh!! People are recommending to use typescript, so I have to learn it.

Setting up typescript environment and start Hello World (before that bit struggle with NPM)
               All YouTube tutorial are using Visual Studio Code, but I want to setup in my Visual Studio Enterprise edition :)

Let’s setup angular2 in Visual Studio
               Spent good amount of time in old angular2 website of Google. Setting up typings.js, common.js, tsconfig.js etc finally with webpack, no idea! What is happening! Confused!!

Try angular2 cli or inbuilt project template with ASP.NET Core 1.0
               Feel that ASP.NET Core 1.0 template is best solution, almost 0 setup and production ready architecture :)

Learn architecture of angular2
               Let’s hands on by writing baby component and understand architecture. Learn data binding, routing, Template, directory bla bla...

Dependency injection in angular2
               Oh.. Not much change with angular 1.X, easy to pick up if u know 1.x

Now, let's implement in memory CRUD/TODO app. And here I am...