The author uses JSP and ASP to programming work. I have been working for a long time. I am more and more, in these two server-side programming solutions, JSP's function is much better than ASP. Why do I want to choose the JSP as my main server-side application to write tools? Of course, JSP is fascinating, but the label library is one of the most important causes of this decision.
Why do you say this way? There are two reasons: maintenance and development speed. The server-side scripting language is actually a furnace that develops Internet. On a server page, you can easily mix a variety of different script methods and objects. This page is simply a concrete for building web. It is this "material" mixed to give the server-side script powerful information processing power. It allows server-side programmers to develop dynamic, flexible web pages. However, on the other hand, the free mixing of scripts is difficult to maintain, especially as the project size is growing, especially. We will have to let the experienced programmers to establish and maintain the final product, and the results have become a general web designer. The server-side application is weakened in the final graphic design and implementation. Worse, because these pages have become more complicated, the development speed is also reduced accordingly. Finally, many medium-sized or large server-side web applications can be launched very late and cost cannot be controlled. In addition, after these applications, many vendors must also find qualified programmers to maintain this kind of code like a pot of pasta.
Everyone we want to see such results, so in order to overcome this problem, ASP introduces COM object technology, and JSP provides J2EE as a countermeasure. These solutions are built on the centralized and reusable code library. However, they can be too difficult to use, and there are many time spent. Also, these solutions do not reduce the temptation of the establishment of chaos code. As a result, we can only organize a large, internal structure well-structured development team to use these technologies. This means that although we have currently have the above methods of establishing large projects, medium-scale projects are not patronized by these technologies.
Reality is that medium-scale projects are the main part of the web application. Therefore, many projects have to face their development and maintenance environments that cannot meet their needs.
Fortunately, JSP provides us with the best solution for solving this problem, and tag libraries provides a simple way to establish reusable code blocks. But the COM and J2EE are different, you don't need to master any additional skills to create a label library: If you will write a JSP page, you will establish a label library. Finally, the label library also improves the maintenance of the web application. This improvement in maintenance is: easily implements XML-based customizable interfaces on the JSP page. The results can be imagined that the web designers can establish JSP web applications without knowing what JSP is going. In this way, Web development has become a very efficient team development task. JSP programmers can establish custom labels and backend code modules, while web designers can use custom labels and fully focus on the web design itself. The label library solves the problem of code confusion, and is clean and beautiful (in fact, XML is to solve the essence of these issues, but the label library still has a considerable role).
