The choice between asp+ and JSP

Asp+|js because I am also an ASP and JSP programmer, I am beginning to write a series of articles to compare the difference between the two, when I wrote half of the asp+ was announced, so I have to start to look at the problem again. I'm doing a JSP project and an ASP project at the same time, which is interesting because it starts with ASP3.0, but when the project is over I will convert to asp+. By then I will be able to have a closer look at asp+ and provide a better comparison of asp+ and JSP. This article is my current understanding and view of asp+, and analyzes its impact on ordinary developers like me.



Through the most preliminary comparisons, I have found that:



1) Object oriented:



asp+ C # as an object-oriented language, in many ways, C # will be Microsoft's Java-like language.



Another interesting part of C # is that all objects automatically become COM objects. If C # has a large market share, it will bring Java-like functionality to the asp+, with faster performance because it can be tightly integrated with the Windows environment.



C # is one of the most important features of asp+ development, and Microsoft will develop C # as a strong competitor to Java. This is also Microsoft. An important part of the NET Framework. I think C # is the main tool for Microsoft to beat its opponents in the programming market. I am looking forward to Microsoft being able to devote all of its energy behind this product, so that C # can be another option for many programmers. The birth of C # will undoubtedly further aggravate the front lines of Microsoft and Sun products, but this is good for users, who can choose between the two to develop new applications.



2) Database connection:



Another bright spot for ASP is that it uses ADO objects, ODBC, Ole-db, and transaction manager. So ASP Web database application development is very simple. Asp+ has developed more functions because of the ado+! Ado+ brings more powerful and faster functionality. JSP and JDBC are now a bit behind the asp/ado compared to the ease of use and performance, and the difference will be more pronounced when the new version asp+/ado+ occurs. So I personally hope that Sun should be able to take great pains to catch up with asp+/ado+.



3 Large Site Application:



Asp+ will have better support for large sites (Web farms). In fact, Microsoft has made great efforts in this regard. Asp+ allows you to consider the situation of multiple servers (multiple servers), when you need more powerful functionality, just add a single server. Whole. NET Framework has fully provided this approach. Asp+ provides external session states (external sessions State) to provide support for built-in Web farm. In addition, because the requested components are fully optimized between each other, they are fast.



So asp+ can now have the same capabilities as JSP in large projects. Asp+ also has a price advantage, since all components will be part of the server's operating system. For JSP, you need to buy expensive application server groups to achieve the same goal.



4) asp+ also offers additional new features, such as:



* Built-in object caching and page result caching.



* Built-in XML support, which can be used for simple processing of XML datasets.



* Server control provides more full interactive control.



This shows that asp+ does have a large development of ASP.



After examining asp+, my preliminary conclusion is that my future projects will mainly use java/jsp based technology. This has the following three reasons:



1 to really play asp+ potential, you want to use C # or vb.net. Both languages will become the core scripting language of the asp+ standard. This is good for the future development of ASP. I never liked to make COM objects with my current Visual Basic. The new asp+ core scripting language is more capable of asp+ value.



It is clear that the new developments in all these asp+ have led me to make a decision on the future of language choices, which will occupy my countless time and effort in the future.



In retrospect, I was learning Java when Java started to develop, and I had a hunch that this would be the language surrounding my future programming career. As a result, JSP naturally became my first choice in web development.



Now that I'm a JSP fan, unless Microsoft can turn me around, I feel like I'm facing a huge asp+ challenge.



2 asp+ is still completely locked in Microsoft's operating system. JSP has a larger scope than asp+, and it also has a good scalability in other server configurations. While the advantages of Windows 2000 are increasingly revealing, this does not pose a problem for developers.



3 I am not sure whether I can agree with the various aspects of asp+ structure, which requires more in-depth analysis, so I hesitate. Maybe I won't change my mind until I use it for 1-2 months. In general, this requires a very high level of view of the beta product.



And as an ASP developer, asp+ also let me stop to reflect. The next 8 months of ASP new projects will become very difficult. Why? Because asp+ and C # pose a challenge, they will not be officially available until 2001. And a lot of performance requirements need to be identified now. Since asp+ is just a beta software, my first choice is very simple now. Now the project is using ASP3.0. I don't think the language of the various beta editions is believable.



But I can not ignore asp+, because it will soon be launched, and represents the future of the ASP. The manager of an ASP project also needs to take into account the future smoothness of portability and the cost of time to pay. Another result is that this makes it more reliable to use PHP and JSP instead of ASP in the near future.



Overall



1 If you use asp+, you will spend extra time learning some new tools.



2 new tools need to be versioned, so why not focus on what's present?



3) asp+ will have the feature JSP already owned.



4 asp+ lock you into a pure Microsoft system.



Finally, I predict a lot of people will join the PHP and JSP ranks. However, there will still be some people will be affected by the asp+ to the industry's excitement. I never saw a beta programming product that would be such a shock!



At the same time, I noticed that the same problem was mentioned in a discussion. NET article:



Asp+ started with free software and is now becoming one of the cornerstones of Microsoft's. NET Framework. Sun should learn from it. The special note is that you need a license to upgrade to asp+ because it integrates with too many products. NET Framework is too large. I usually wait for its first service pack before assuming that a product can be a real product. So even though asp+ has been versioned in the first quarter of 2001, I still have to wait until the second quarter of 2001.



Of course, because asp+ has been so exciting, once launched, many stores will immediately provide asp+.



Actually, I've already used the beta version of asp+!. I found that it uses the. aspx suffix, which makes me feel that Microsoft will launch the first asp+ service pack in the near future.



Next year, we'll see how sun and Microsoft are going to battle in this huge market, and what are the choices programmers will make?