In this post, I want to cover a Closure optimization meant to help us preventing memory leaks. This optimization is implemented by the three major browsers: Chrome, Firefox and IE.
Closure is a popular subject and you can find very good articles out there.
Although the post won't cover Closures internals, I will briefly cover the basics in order to keep the reading fluent.
Basics
To put it shortly; any time we access a method in JS, a special context object is created. This object contains the variables to be searched in the scope chain search process.
var x = 10;
(function parentFunc () {
console.log(x);
}()); //* Result: 10
The code above will print 10 because when the parentFunc method is executed, a special context object containing its parent's variables is created and is pointed by parentFunc method scope.
When the interpreter starts searching for 'x' value it searches inside the parentFunc scope. If it can not find it, its parent scope gets evaluated. …
In this post I will go over some interesting HTTP topics: HTTP Caching Headers, SSL, Fiddler, and how each of them can have impact over your web application performance (yes, just running Fiddler on your machine can effect your application's caching behavior!). The main purposes of this post are both, helping out other developers who encountered issues covered in the post, and to stimulate awareness about security and HTTP caching relationship. For .NET Stack developers, don't be disappointed when I will mention Spring MVC, it is just my current REST provider (long live IIS!), the essence of the post should be interesting regardless. NOTE: When mentioning 'browser' I am referring by default to Chrome version 51.0.2704.84. Basic HTTP Caching Headers Rules I won't fully cover basic HTTP Caching protocol subjects like Etag/Last-Modified, no-store, no-cache etc. But before staring let's have a very quick reminder about basics HTTP Caching concepts: no-cache - must revali…