In the early days of the Web, Web pages were static in nature. This implies that the content displayed in a static Web page couldn't change. In addition, static Web pages that used HTML alone were not interactive; therefore, they could not retain users' attention for a long time. As a result, dynamic Web pages that could present data from an external source, such as a database, were developed. The content in such a Web page is dynamic; therefore, when the data in the underlying data source is changed, the modified data can be reflected in the dynamic Web page.
You can create dynamic Web pages in several ways. You learned to create dynamic Web pages by using Visual Studio .NET in "Building Web Applications on the .NET Platform." You can also create dynamic Web pages by using Common Gateway Interface (CGI) scripts and applications.
CGI applications are compiled applications that are developed by using languages, such as C or C++. The CGI technology is used to create high-performance applications that are deployed on servers based on operating systems, such as Unix.
Deploying CGI applications on servers using the Windows platform is an overhead. This is because CGI applications are executable files created using various programming languages. Whenever a CGI application is deployed on a Windows environment, the operating system assigns a process to the file. Processes require a large number of resources; therefore, they increase the overall cost of deploying the application. In addition, the process overhead associated with each CGI call makes CGI applications non scalable. Therefore, to create high-performance multithreaded Web applications for the Windows platform, Microsoft came up with the Internet Services Application Programming Interface (ISAPI) technology. ISAPI is an API that extends the functionality of the Web server, such as IIS.
Although ISAPI applications are high-performance applications, they are not widely used because Visual C++ 6.0 offers limited support for creating ISAPI applications. As a solution to this problem, Microsoft created an MFC-based wizard for ISAPI extensions. However, the wizard did not include support for standard Web features, such as session management and cookies. In addition, the wizard did not provide a built-in support for accessing database from the application. To provide a solution in the form of a simpler COM component development environment, Microsoft developed the ATL Server. The following section provides an overview of the ATL Server.
XML Related Interview Questions
|Soap Tool Interview Questions||HTML Interview Questions|
|PHP Interview Questions||ASP.NET Interview Questions|
|PHP5 Interview Questions||Java Interview Questions|
|CSS Interview Questions||XSLT Interview Questions|
|Java XML Interview Questions||XMLHttpRequest (XHR) Interview Questions|
|ebXML Interview Questions||XML DOM Interview Questions|
|XML-RPC Interview Questions||XSD Interview Questions|
|Soap Web Services Interview Questions||XSL Interview Questions|
|Xml Publisher Interview Questions|
Basics Of Xml
Basics Of Web Services
Introduction To Soap
Introduction To Uddi
Introduction To Wsdl
Creating A Web Service Using The Microsoft Soap Toolkit
Building Web Applications On The .net Platform
Creating An Asp.net Web Service
Creating A Web Service From An Interface
Introduction To The Atl Server
Creating A Web Service Using The Atl Server Library
Design And Creation Of The Knowledge Share Web Service
Introduction To Java Xml Technologies
Developing Java Web Services
Design And Creation Of A Web Service Using The Ibm Toolkit
Introduction To Mobile Applications
Creating A Mobile Application That Consumes A Web Service
Web Services Development With Jdeveloper
Creating Web Services Using Perl
Integration Of Xml Web Services With The Office Xp And Sql
Server 2000 Toolkits
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.