World of code lines-Comparison of Three Ajax frameworks

As Web 2.0 is widely known and accepted by more and more people, as an important part of it, Ajax technology is also being applied by more and more people. However, its complicated development process and low development efficiency make it possible for me to have little experience in traditional web development. Program Personnel are discouraged. Fortunately, the emergence of various Ajax development frameworks greatly reduces the development threshold and improves the development efficiency. Since learning about Ajax in last May, we have also tried the three Ajax frameworks ajax.net, magicajax, and Atlas. Magicajax is widely used in projects due to various factors. With the maturity of Atlas, it is also gradually transferred to Atlas.
Ajax.net appeared earlier and started Source code In the early stage, there should be more use. However, programmers still need to write a lot of JS Code Is not very convenient to use. Then, magicajax emerged and moved a lot of people's eyes. Its function was like its name, A panel can magically prevent the execution events of the controls contained in the panel from refreshing the page, but it is only possible to find that the efficiency is really a big problem. As an Ajax Development Kit tailored by Microsoft for. NET 2.0, Atlas has its inherent advantages. Currently, it has released three CTP versions and has never dared to use them in projects. Recently I made up my mind to use the CTP version of July. It seems to be quite good. It is very powerful (without refreshing the Drag Control and using it with the profile to save it to the database ), provides several extended server controls, and can also easily use client controls to implement full client code execution. With js code, you can easily access web services. The updatepanel control similar to magicajax is also provided with more powerful functions. Although the server events executed in the panel are not refreshed, the request can still be used, response and other environment objects (not in magicajax), some people may think that its JS file is very large, and each download will affect the speed, but from the current usage, the efficiency is much higher than that of magicajax, and JS files are not downloaded every request. Although there are still some bugs, they can be applied initially. Current Community The discussion is still concentrated on ww.asp.net forums and some blogs outside China (there is a link on atlas.asp.net). Here we recommend that the flier's blog is also launching Atlas implementation mechanism analysis. Article .
Ajax does not find a satisfactory answer to the client environment requirements on the Internet. Although most Ajax technologies use XMLHTTP objects, asynchronous access is not refreshing. Ie5 and later support XMLHTTP objects. Today, I tested and accessed several Ajax applications in Windows 98 and ie5.5, but I found that none of them can work very well. Accessing Gmail won't be able to enter the inbox at all. When it reaches "loading", it will die there. Accessing the ajax.net demo will cause a script error, and the Code cannot be executed at all. Access the magicajax demo, the code can be executed normally, but to refresh the page, there will also be a script error. The cascade drop-down box in updatepanel for accessing Atlas can also run normally, but the page also needs to be refreshed and a script error is prompted. However, it is impossible to use the function of directly calling Web service using Js. Therefore, Ajax has high requirements on the client.