Advantage of using ASP and where to use

Classic ASP runs on the server, so it is useful for work that must happen before the response is sent to the browser: reading form data, applying business rules, working with sessions, accessing a database, and generating HTML dynamically.

 Copy<%@ Language=VBScript %>
<%
Response.Write "Server date: " & Date()
%>

Where server-side ASP helps

• Keep database credentials and server-side logic away from the browser.
• Generate different output for different users or requests.
• Validate and process submitted data on the server.
• Work with sessions, files, COM components, and databases available to the IIS application.

What ASP cannot do after the response is sent

Once IIS has finished processing the page and the browser has received the response, Classic ASP is no longer running for that request. Browser interactions such as opening a client-side alert, reacting immediately to a click, or changing the page without another request are handled by HTML, CSS, and JavaScript.

For important validation, use server-side checks even when JavaScript also validates the form. Client-side validation improves usability, but it must not be the only protection for data sent to the server.

See server-side vs client-side tasks for practical examples.

Back to top ↑

Subhendu Mohapatra

Author & Instructor at plus2net

I write and maintain practical tutorials on Python, PHP, SQL, JavaScript, HTML, jQuery, and web development at plus2net. The tutorials focus on clear explanations, working examples, and code that readers can test and adapt while learning.

About the author   Watch on YouTube

Connect: