Server-side scripting: Difference between revisions

Content deleted Content added
Jtbwikiman (talk | contribs)
m Link inserts and very minor copyediting
PrimeBOT (talk | contribs)
m Task 24: elink template removal following a TFD
Line 6:
}}
 
'''Server-side scripting''' is a technique used in [[web development]] which involves employing [[Scripting language|script]]s 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|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.
Line 20:
 
== Explanation ==
In the earlier days of the web, server-side scripting was almost exclusively performed by using a combination of [[C (programming language)|C]] programs, [[Perl]] scripts, and [[shell script]]s using the [[Common Gateway Interface]] (CGI). Those scripts were executed by the [[operating system]], and the results were served back by the [[web server]]. Many modern web servers can directly execute on-line [[Scriptingscripting language|scripting languages]]s such as [[Active Server Pages|ASP]], [[JavaServer Pages|JSP]], [[Perl]], [[PHP]] and [[Ruby (programming language)|Ruby]] either by the web server itself or via extension modules (e.g. [[mod_perl]] or [[mod_php]]) to the webserver. For example, [[WebDNA]] includes its own embedded database system. Either form of scripting (i.e., CGI or direct execution) can be used to build up complex multi-page sites, but direct execution usually results in less overhead because of the lower number of calls to external interpreters.
 
Dynamic websites sometimes use custom web application servers, such as [[GlassFish|Glassfish]], [[Plack (software)|Plack]] and [[Python (programming language)|Python]]'s "Base HTTP Server" library, although some may not consider this to be server-side scripting. When using dynamic web-based scripting techniques, developers must have a keen understanding of the logical, temporal, and physical separation between the client and the server. For a user's action to trigger the execution of server-side code, for example, a developer working with classic ASP must explicitly cause the user's browser to make a request back to the webserver.
Line 27:
 
== Server-side rendering ==
With the advent of [[Singlesingle-page application|single-page applications]]s, an updated approach to server-side scripting was introduced, known as server-side rendering. With server-side rendering, static HTML can be sent from the server to the client, and client-side JavaScript then makes the web page [[Dynamic web page|dynamic]] by attaching event handlers to the HTML elements in a process called [[Hydration (web development)|hydration]]. Examples of frameworks that support server-side rendering are [[Next.js]], [[Nuxt.js]], [[Angular (web framework)|Angular]], and [[React (JavaScript library)|React]].
 
An alternative to server-side rendering is [[Static site generator|static site generation]]. With server-side rendering, the page is generally assembled on the server once per each request. By contrast, with static site generation, the application generates all the static HTML pages at build time. These pre-built pages are then sent to the client at each request, without having to build them again. This leads to faster rendering times, since a new page doesn't have to be generated on every request; the server simply hands over a file it already generated in the past. The downside is that when some data on the page changes, it needs to be rebuilt. Examples of static site generation tools are [[Jekyll (software)|Jekyll]] and [[Gatsby (software)|Gatsby]]. Sites generated by static site generation tools are often hosted on [[Netlify]] or [[GitHub]] pages.
Line 75:
== External links ==
{{Wikiversity | Server-Side Scripting}}
;
* {{curlie|Computers/Programming/Internet/Server_Side_Scripting}};
 
{{Web interfaces}}