Server-side scripting: Difference between revisions

Revision as of 15:48, 12 March 2025

Revision as of 18:27, 16 March 2025

Line 6:

}}

'''Server-side scripting''' is a technique used in [[web development]] which involves employing [[Scripting language|script]]sscripts on a [[web server]] which produces a response customized for each user's (client's) request to the website. Scripts can be written in any of a number of server-side scripting languages that are available. Server-side scripting is distinguished from [[client-side scripting]] where embedded scripts, such as [[JavaScript]], are run client-side in a [[web browser]], but both techniques are often used together. The alternative to either or both types of scripting is for the web server itself to deliver a [[static web page]].

Server-side scripting is often used to provide a customized [[User interface chrome|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, whereas, with client-side scripting, the user has access to all the code received by the client. A downside 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 prevent the use of the application when the user is disconnected from the server.

When the server serves data in a commonly used manner, for example, according to the [[Hypertext Transfer Protocol|HTTP]] or [[File Transfer Protocol|FTP]] [[Protocol (computing)|protocols]], users may have their choice of a number of client programs (most modern web browsers can request and receive data using both of those protocols). In the case of more specialized applications, programmers may write their own server, client, and communications protocol, that can only be used with one another.

Programs that run on a user's local computer without ever sending or receiving data over a network are not considered clients, and so the operations of such programs would not be considered client-side operations.