Server-side scripting: Difference between revisions

Revision as of 17:56, 7 May 2024

Revision as of 06:27, 2 June 2024

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 (see below). 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 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 26:

Server-side scripts are completely processed by the servers instead of clients. When clients request a page containing server-side scripts, the application server processes the scripts and returns an HTML page to the client.

== How to Server-side script Approachesrendering ==

With the advent of [[Singlesingle-page application]]s, a new approach was introduced to generate the HTML using the client application, but on the back end. Examples of frameworks that use [[Server-side rendering|SSR]] are [[Next.js]], [[Nuxt.js]] and [[Nest.js]]. They use [[React.js]], [[Vue.js]], and [[Angular (web framework)|Angular]], respectively, to generate the content of the server.

Server-sideAn generation,alternative orto SSG,server-side rendering is an[[Static alternativesite togenerator|static SSRsite generation]]. With server-side rendering, the page is generally assembled on the server once per each request. By contrast, with SSGstatic 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.

=== Server-side generation ===

Server-side generation, or SSG, is an alternative to SSR. With server-side rendering, the page is generally assembled on the server once per each request. By contrast, with SSG, 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.

File generation can happen on a completely different computer, for example using [[continuous delivery]]. Example of SSG tools are [[Jekyll (software)|Jekyll]], [[Gatsby (software)|Gatsby]] or [[Eleventy (software)|Eleventy]]. Those sites are often hosted on [[Netlify]] or [[GitHub]] pages. GitHub also supports Jekyll projects where it automatically build the site when changes are added to [[gitGit]].

== Languages ==