【正文】 原文： （一） An Active Server Page (ASP) 1. This paper firstly introduces multitier B/S Architecture and Webrelated technology .Based on them , this paper presents system objection, system demand, main feather and system design solution ,particularly describes system design and implement in detail. In system design and implement， and key points in other subsystem are also analyzed further .This paper also introduces mostly technology of system . Lastly, this paper makes a summery and figures out some problem which need to be improved. 2. puting has brought about a whole new standard of corporate co mputing productivity, but at the same time it has introduced many new problems for corporate IT anizations. The advent of lowcost desktop puters makes B/S possible. No longer is it necessary for users to wait even seconds to interact with their corporate data. With their own puter on their desktop they do not need to wait for the mainframe to respond. All of this cheap puter power has also made it possible to support putation intensive graphical interfaces, which are much easier for users to understand. In order for B/S to work, the application program which used to reside entirely on the mainframe has been split into two pieces, the client piece and the server piece. The portion of the application that resides in the Client personal puter includes logic for the presentation of information to the user and mechanisms for accepting user input. It also includes logic for data interaction at the Client, such as changing the appearance of the graphical interface as the user make various choices. The Client software often includes corporate business rules that allow data to be validated before it is sent to the server. The portion of the application that remains on the Server is usually just the portion that stores data at a central location, accessible to other users. The once mighty mainframes have been reduced to database servers, while the rest of the application has migrated out to the clients. This migration has caused many problems. The Client machines have bee fat. As the plexity of applications has risen it has bee necessary to supply users with more and more powerful puters with faster processors, more disk storage, and more RAM. It is true that personal puter manufacturers have been able to deliver better and better puters for the same amount of money, but the constant upgrades required are costly for corporations. It takes more people and time to upgrade hundreds or thousands of personal puters than it used to take to just upgrade the mainframes. Setting aside the cost of Client equipment, the proliferation of corporate applications, including business logic, to hundreds or thousands of machines has bee a major cost factor for corporations. Where IT staffs used to be able to maintain all the corporate software assets in one central location, they now need to maintain corporate software spread all across the corporation, often housed in puters that are out of IT control. There are many estimates available that the cost of Client/Server puting is eight or more times the cost of the equipment alone. Several panies offer large, expensive systems that have the sole purpose of maintaining corporate software spread out all over the corporation. The issue here is not personalproductivity software such as word processors and spreadsheets. Personal software products have enabled knowledge workers to attain new heights of productivity. The issue is the maintenance of corporate software, such as orderentry and accounting. Imagine the difficulty of making a schema change in a corporate database, and synchronizing that change with the updating of thousands of copies of the corresponding Client software. It is true that the use of departmentlevel LANs can bring down the number of copies that need to be updated to hundreds, instead of thousands. The size of the LANs must be limited, because the large size of the fat client software requires a responsive LAN or else the users will just copy the enterprise software to their own machines, bringing us back to thousands of copies to be maintained. The task of making simultaneous changes to even hundreds of copies of client software is still a daunting one. 3. which in turn serves it back to the client in your personal puter, which displays the information for you. The client/server model has bee one of the central ideas of work puting. Most business applications being written today use the client/server model. So does the Inter39。s main program, TCP/IP. In marketing, the term has been used to distinguish distributed puting by smaller dispersed puters from the monolithic centralized puting of mainframe puters. But this distinction has largely disappeared as mainframes and their applications have also turned to the client/server model and bee part of work puting. In the usual client/server model, one server, sometimes called a daemon, is activated and awaits client requests. Typically, multiple client programs share the services of a mon server program. Both client programs and server programs are often part of a larger program or application. Relative to the Inter, your Web browser is a client program that requests services (the sending of Web pages or files) from a Web server (which technically is called a Hypertext Transport Protocol or HTTP server) in another puter somewhere on the Inter. Similarly, your puter with TCP/IP installed allows you to make client requests for files from File Transfer Protocol (FTP) servers in other puters on the Inter. Other program relationship models included master/slave, with one program being in charge of all other programs, and peertopeer, with either of two programs able to initiate a transaction. ASP is also an abbreviation for