Difference between revisions of "Server-side scripting"

From Wiki @ Karl Jones dot com
Jump to: navigation, search
(First)
(No difference)

Revision as of 11:06, 24 May 2015

Server-side scripting is a technique used in web development which involves employing scripts on a web server which produce a response customized for each user's (client's) request to the website.

Many different server-side scripting languages exist, some general-purpose, some with specialized purposes

Popular languages include:

Server-side scripting is often used to provide a customized interface for the user. These scripts may assemble client characteristics for use in customizing the response based on those characteristics, the user's requirements, access rights, etc.

Server-side scripting also enables the website owner to hide the source code that generates the interface.

Static web pages

The alternative is for the web server to deliver a static web page -- a single file that the source code for the page.

== Disadvantages

A down-side to the use of server-side scripting is that the client needs to make further requests over the network to the server in order to show new information to the user via the web browser.

These requests can:

  • Slow down the experience for the user
  • Place more load on the server (and load means money because server activity uses electricity)
  • Prevent use of the application when the user is disconnected from the server.

Server-side scripting is different from client-side scripting where embedded scripts -- notably JavaScript -- are run client-side in the user's web browser.

Server-side and client-side techniques are often used together in a coordinated manner.

External links

  • [] @ Wikipedia