As you
all know that HTML is static, so when two HTML pages want to communicate
they need server-side program, and if you want to maintain user identity
then you have to implement it using server session management.
The server can monitor
users (e.g. it can collect usage statistics).
The server can control
users (e,g, it can stop
certain users from accessing information).
As
the program is executed on the server, it is browser independent, so you
can choose any of the server-side programming languages to program.
It is suitable for
applications with centralised information (e.g. databases).
In general, it is
easier to write server-side programs than client-side ones
As the server-side
program is executed on the server, the code is not visible to the user, so
you can implement password validation and other secure features.
Disadvantages:
As all the requests
are sent to the server for processing, the server can be slow to respond
and so it can become a bottleneck.
As each request is
sent to the server, the process takes longer to respond, it could be due
to the network speed and other reasons.
Server-side programs
typically have less sophisticated user interfaces than client-side
programs.
Examples
of Server-side programming
Dynamically
edit, change or add any content of a Web page
Respond
to user queries or data submitted from HTML forms
Access
any data or databases and return the results to a browser
Customize
a Web page to make it more useful for individual users
The
advantages of using ASP instead of CGI and
Perl, are those of simplicity and speed
Provides
security since your ASP code can not be viewed from the browser
Since
ASP files are returned as plain HTML, they can be viewed in any browser
Clever
ASP programming can minimize the network traffic