Author: Casey Kochmer
Because I am also an ASP and JSP programmers, I started writing a series of articles to compare the differences. When I wrote half, ASP was announced, so I went to examine this issue again. I am doing a JSP project and an ASP project, the latter is very interesting, because it starts to use ASP3.0, but when the project is over, I will convert to ASP . At that time, I will have a closer look to ASP and provide better ASP and JSP comparisons. This article provides a preliminary observation for ASP , and its impact on a general developer like me.
Through the initial comparison, I found that: 1) Objective: ASP uses C # as an object-oriented language, in many ways, C # will become Microsoft's similar language similar to Java. C # Another interesting place is that all objects are automatically turned into a COM object. If C # can achieve a lot of market share, it will bring ASP to Java features and have faster performance because it can be tightly integrated with the Windows environment. C # is an ASP development one of the most important features, Microsoft will develop C # to become a strong opponent in Java. This is also an important part of their .NET framework. I think C # is Microsoft to defeat the opponent's main tool in the programming market. I look forward to Microsoft's ability to pour full of this product so that C # can be another choice for many programmers. The result of C # generated is to further reinforce the front of Microsoft and Sun products. This is advantageous for users, they can choose one of both to develop new applications.
2) Database connection: ASP Another highlight is that it uses ADO objects, ODBC, OLE-DB, and Transaction Manager. Therefore, ASP Web database application development is particularly simple. ASP has developed more features because of ADO ! ADO brings more powerful and faster features. JSP and JDBC currently have some backward compared to ASP / ADO, which will be more obvious when new version ASP / ADO appears. I personally hope that Sun should spend vigorous effort to catch up with ASP / ADO .
3) Large site applications: ASP will have better support for large sites (Web Farms). In fact, Microsoft has a huge effort in this regard. ASP allows you to take into account the multiple Servers, when you need more powerful features, just add a server. The entire .NET framework has fully provided this method. ASP provides external session state to provide support for built-in Web Farm. In addition, since the requested components have passed full optimization, the speed is very fast. So ASP can now have equivalent capabilities as JSP in large projects. The ASP has the advantage of price because all components will be part of the server operating system. For JSP, you need to buy an expensive application server group to achieve the same purpose.
4) ASP also provides more new features of other aspects. For example: * Built-in object cache and page results cache. * Built-in XML support can be used for simple processing of XML datasets. * Server control provides more fully interactive control. ASP does develop significantly to ASP.
After I reviewed ASP , my preliminary conclusion is: My future project is mainly to use Java / JSP technology. This has the following three reasons: 1) To truly play ASP potential, you have to use C # or VB.NET. Both languages will become the core scripting language of the ASP standard. This is very beneficial for the future development of ASP. I have never like to make COM objects with current Visual Basic. The new ASP core scripting language can make the value of ASP . Obviously, all of these ASP new progress has prompted me to make a decision on future language choices, which will occupy my future countless time and efforts. When Java developed up, I learned Java, then I premonged this will be a language around my future program career. Thus, JSP becomes the first choice I am in web development. When my current ASP project is completed, I will reconsider whether C # is in line with my programming tool system. Now I am already a JSP FAN unless Microsoft can turn my entire twist, I guess I is facing a huge challenge of ASP . 2) ASP is still fully locked in Microsoft's operating system. JSP has a larger range than ASP , which also has good scalability in other server configurations. Although the advantages of Windows 2000 is increasing, this does not constitute a problem for developers.
3) I can't be confident that I can agree with the various aspects of the ASP structure, which requires more in-depth analysis, so I hesitate. If I use it for 1-2 months, I may change the view. Overall, this requires this Beta product in a high level. As an ASP developer, ASP let me stop. ASP new projects in the next 8 months will become difficult. why? Because ASP and C # bring a problem, they are officially available until 2001. And many performance requirements need to be determined now. Since ASP is just a beta software, now my first choice is very simple. The current project is adopted. I think the language of various Beta version is not trustworthy.
But I can't ignore the ASP because it will soon be launched and represent the future of ASP. Managers from ASP projects also need to take into account future slip portability and time cost, etc. Another result is that this seems to use PHP and JSP in the near future to reserve ASP more reliable. In general, 1) If you use ASP , you will take additional time to learn some new tools. 2) The new tool has to be versioned, so why don't you pay attention to what you present? 3) ASP will have the feature JSP that will have. 4) ASP Locks you into Microsoft's system. (I read a story about Microsoft to transplant the .NET to Linux, but I don't feel much trustworthy.) Finally, I predict that there will be many people to join PHP and JSP ranks. However, some people will be infected by the excitement of ASP to the industry. (I have never seen a Beta programming product will bring such shock.)
The following is a related discussion .NET article.
ASP starts with free software, and now it has gradually become one of the cornerstones of Microsoft .NET framework. SUN should be learned from it. Special note is that you need a license to upgrade to ASP because it is integrated with too many products. The .NET frame is too big. Before assumed a product, I usually wait for its first Service Pack. So, even if the ASP has been versioned in the first quarter of 2001, I still wait until the second quarter of 2001. Of course, because ASP has produced such an exciting, once the store is launched, many stores will immediately provide ASP . In fact, I have already used Beta version ASP ! It uses .aspx suffix, which makes me feel Microsoft will launch the first ASP Service Pack in the near future. In the next year, we will see how Sun and Microsoft start the duel in this huge market, and what choices will the programmers do?
