Today, mobile phones have unlimited data plans, the home connections have reached 100 Mbit/s speed heights and to decrease the output size, we just need to tick check box in the IIS, therefore, the output, weather be it the static or the dynamic, is compressed. Therefore, the “HTML optimizers” era of tools, which remove the extra spaces as well as “unneeded” tags from the markup, is over. One more thing, which is helpful in avoiding the traffic jams, was the Ajax. It has killed 2 birds with single shot – with decreased traffic flow through only up or down loading data, the application needs at the time, with that, increased the result time. However, it does have its cost. Every small callback done by the Ajax is just like an ordinary callback, exclude that, it transfers smaller data. However it is still a connection. Here you can see the problem. You are inquiring every individual thing that you request from the server, through sending the individual requests as well as parsing the responses and received files. This overhead is heavy even though the output is cached or compressed on the server.
<link href=”styles/mystyle.css” rel=”Stylesheet” />
you need to type this:
<link href=”styles/css” rel=”Stylesheet” />
Strongly Types the Data Controls – one of the pet upsets around the non-MVC ASP.NET databinding is “bind and hope” concept, which Eval has. It always felt bit crappy – hopefully it will change now.
Click and create new event – This is a nice solution to a small irritation, no more typing fortified void the btnMyThingie_Click – sometimes, the small things make big differences in your everyday work flow.
Interesting point about new features of the ASP.NET is when they are presented; they produced massive recoil from the people using the 3rd party libraries for achieving same functionality. Its reason is completely psychological. Evidently, some projects have to die. But that’s how it goes!