In today's article, we want to address the topic of Active Server Pages, a topic that has caused a great impact on today's society. Active Server Pages is an issue that affects people of all ages, genders and cultures, so it is important to analyze it from different perspectives. Throughout this article, we will explore the origins of Active Server Pages, its evolution over time, and its influence on various aspects of everyday life. Additionally, we will examine possible solutions or approaches to address this issue effectively. We hope that this article generates reflection and debate among our readers, as well as provides valuable information about Active Server Pages.
This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)
|
Developer(s) | Microsoft |
---|---|
Stable release | 3.0
/ February 17, 2000 |
Type | Web application framework |
License | Proprietary software |
Website | www |
Filename extension |
.asp |
---|---|
Developed by | Microsoft |
Active Server Pages (ASP) is Microsoft's first server-side scripting language and engine for dynamic web pages.
It was first released in December 1996, before being superseded in January 2002 by ASP.NET.
Initially released as an add-on to Internet Information Services (IIS) via the Windows NT 4.0 Option Pack (1996), it is included as a component of Windows Server (since the initial release of Windows 2000 Server). There have been three versions of ASP, each introduced with different versions of IIS:
ASP 2.0 provides six built-in objects: Application, ASPError, Request, Response, Server, and Session. A Session
object, for example, represents a session that maintains the state of variables from page to page. The Active Scripting engine's support of the Component Object Model enables ASP websites to access functionality in compiled libraries such as dynamic-link libraries.
ASP 3.0 does not differ greatly from ASP 2.0 but it does offer some additional enhancements such as Server.Transfer method, Server.Execute method, and an enhanced ASPError object. ASP 3.0 also enables buffering by default and optimized the engine for better performance.
ASP was supported until 14 January 2020 on Windows 7. The use of ASP pages will be supported on Windows 8 for a minimum of 10 years from the Windows 8 release date. ASP is currently[when?] supported in all available versions of IIS.
ASP uses scripting on the server to generate content that is sent to the client's web browser via HTTP response. The ASP interpreter reads and executes all script code between <% and %> tags, the result of which is content generation. These scripts were written using VBScript, JScript, or PerlScript. The @Language
directive, the <script language="language" runat="server" />
syntax or server configuration can be used to select the language. In the example below, Response.Write Now() is in an HTML page; it would be dynamically replaced by the current time of the server.
Server side | Client Side |
---|---|
The server's current time:
<%
Response.Write Now()
%>
|
The server's current time:
8/11/2015 6:24:45 PM
|
Web pages with the .asp filename extension use ASP, although some web sites disguise their choice of scripting language for security purposes by using the more common .htm or .html extensions. Pages with the .aspx extension use compiled ASP.NET; however, ASP.NET pages may still include some ASP scripting. The introduction of ASP.NET led to use of the term Classic ASP for the original technology.
Sun Java System ASP (formerly ChiliSoft ASP) was a popular and reportedly complete emulator, but it has been discontinued.
The server object allows connections to databases (ADO), filesystem, and use of components installed on the server.
<%
Dim oAdoCon, oAdoRec, oAdoStm, oCdoCon, oCdoMsg, oSciDic, oSciFsm, oMswAdr
Set oAdoCon = Server.CreateObject("ADODB.Connection")
Set oAdoRec = Server.CreateObject("ADODB.Recordset")
Set oAdoStm = Server.CreateObject("ADODB.Stream")
Set oCdoCon = Server.CreateObject("CDO.Configuration")
Set oCdoMsg = Server.CreateObject("CDO.Message")
Set oSciDic = Server.CreateObject("Scripting.Dictionary")
Set oSciFsm = Server.CreateObject("Scripting.FileSystemObject")
Set oMswAdr = Server.CreateObject("MSWC.Swingbridge")
%>
This object stores global variables, which are variables accessible to all users.
<%
Application("Ali") = "My ASP Application"
Response.Write "Welcome to " & Server.HTMLEncode(Application("Ali")) & "!"
%>
Stores variables accessible only to a single visitor, which are local variables.
<%
If Len(Request.QueryString("name")) > 0 Then
Session("name") = Request.QueryString("name")
End If
Response.Write "Welcome " & Server.HTMLEncode(Session("name")) & "!"
%>
The session object is file based and multiple concurrent read and/or write requests will be blocked and processed in turn.
Allows the management and fixing of non-fatal errors.
<%
On Error Resume Next
Response.Write 1 / 0 ' Division by zero
If Err.Number <> 0 Then
Response.Write "Error Code: " & Server.HTMLEncode(Err.Number) & "<br />"
Response.Write "Error Source: " & Server.HTMLEncode(Err.Source) & "<br />"
Response.Write "Error Description: " & Server.HTMLEncode(Err.Description) & "<br />"
Err.Clear
End If
%>