What is web scripting?
Scripting is an integral part of web development. Using powerful scripting languages like JavaScript and PHP, developers can create the dynamic web content we enjoy every day.
But what are the key differences between client-side scripting and server-side scripting, and how do they actually work?
In the context of websites and applications, the client refers to a web browser (like Chrome or Firefox) running on the user’s local machine. The server is, well, the server, obviously. Or to be more accurate, it’s the web server software such as Apache or NGINX running on dedicated server hardware.
Katie Collins
Dynamic and static web content
‘Dynamic’ web content is anything that isn’t just a static page, i.e. any content that displays in different ways for different users at different times; from simple clocks and drop-down menus to complex interactive forms.
While static content can be generated by a single HTML document, created once and never updated, dynamic sites rely on scripting to serve up a new experience every time.
Scripting languages like JavaScript and PHP allow complex tasks to be automated and executed on the fly, resulting in the advanced functionality we now take for granted on popular websites.
But the question is, where does the scripting happen? While the client and the server are both capable of running different types of scripting to generate dynamic content, the implementation is very different on each side.
What is client-side scripting?
Running in the user’s browser, client-side scripting generates dynamic content by processing the code received from the server. Usually this consists of JavaScript, combined with HTML and CSS.
There are a wide range of client-side frameworks available, including React.js (from Facebook) and Angular (from Google). Some frameworks combine client-side and server-side scripting, like Vue.js and Laravel. These work well together and can make the creation of a complete application far less painful, with lots of helpful tutorials available.
Advantages of client-side scripting
Once a page is loaded, client-side scripting doesn’t require any additional help from the server – all the work is done by your browser on its own. Client-side scripting can respond to user input to display different content based on specific actions, but all the actual data has to be provided by the server beforehand.
Sites that use a lot of client-side scripting can perform well and take some of the load off the server, but it can also be difficult to implement advanced functionality using client-side techniques alone.
Disadvantages of client-side scripting
There are however a few disadvantages to client-side scripting. Different browsers support scripts in different ways, especially if a browser is not up to date, this means more testing is required when using client-side scripts. Some browsers may not support the script altogether and this can cause an issue on the users end.
There are also some issues in terms of security, as technically anyone can check the code, which can also serve as a disadvantage.
What is server-side scripting?
The most popular server-side scripting languages and frameworks include:
- PHP
- ASP.NET
- Node.js
- Java
- Ruby
- Perl
- Python
These scripts run on a web server and respond to client requests via HTTP to deliver dynamic and customised content to the user. More importantly, server-side scripting is required to access or store persistent data like user profile information; whether it involves pulling data from a file server, database or mail server, this can all be done with a server-side scripting language like PHP.
Advantages of server-side scripting
One of the key differences between the client and server-side scripting is that server-side code is always responsible for providing and storing any resources needed by the client. This can either be done as the page loads, or interactively as the user makes requests and changes (using techniques such as AJAX – more on that below). This means the source code from server-side scripting is usually completely hidden from the end user.
For example, PHP is executed exclusively on the server to generate HTML that is in turn rendered by the client – your browser never actually sees any PHP code. Even if you click ‘View page source’, you’ll only see the HTML, not the PHP scripting that generated it.
It’s critical that the back-end server authenticates any client-side request prior to accessing or updating any resources; the fact that client-side scripting languages such as JavaScript run in the browser means the user can alter the code, sometimes with malicious intent. Therefore, never trust client-side data unless it can be properly authenticated. There are many techniques for supporting authentication, with JSON Web Tokens being one of the most popular solutions.
One of the downsides of server-side scripting, however, is that, simply put, it means more work for the server. Lots of scripts running on the server can result in slower performance, especially when client requests to the server occur frequently.
Disadvantages of server-side scripting
On the other hand, there are also some disadvantages of server-side scripting. One major disadvantage is that server-side scripts require an immense amount of processing power, and this can slow down the website if you’re operating on a slow server. Another factor to consider is that the scripting software will have to be installed directly onto the server, so it’s vital that you have a server that can handle this.
That’s why it’s always important to use the correct server for your projects.
What is the main difference between client and server-side scripting?
Let’s quickly run through the main difference between the two.
Whilst server-side scripts are enacted by the web server itself, a client-side script occurs only on a user’s browser. The server-side is reacting to the client’s request and will then show them the content they want to see via the client-side. These two scripting sides collaboratively take care of both the front and back end.
Client-side and server-side scripting: front-end vs back-end
The terms ‘front-end’ and ‘back-end’ are often used interchangeably with client-side and server-side, respectively. But this isn’t totally accurate. Front-end development involves all the things the user sees and interacts with, making web design and user experience key concerns. Back-end development covers basically everything else, including the server and databases.
In practice though, front-end development is usually focused on client-side scripting techniques that make use of HTML, CSS and JavaScript, while web-server scripting languages remain more relevant to back-end developers.
Why you should use both client and server-side scripting
For a well-optimised, quick-loading website, a balance between client-side and server-side scripting is generally recommended. Really, both sides are needed to create properly dynamic content, since there are certain things the client can do that the server can’t, and vice versa. The actual implementation, including the scripting languages used, will always depend on the needs of your application.
AJAX: bridging the client-server gap?
AJAX (Asynchronous JavaScript and XML) is a technology that uses client-side JavaScript to handle user input, while transferring data to and from the server in the background (asynchronously).
This combination of server-side and client-side scripting languages enables individual parts of a webpage to be updated almost instantly, without having to load a whole new page. You can see AJAX in action on interactive sites and applications like Google Docs that allow users to dynamically edit and save content.
Looking for the ideal environment for your scripting language of choice? With Fasthosts cloud servers, you can easily launch your project with PHP, Perl, Node.js or Python. Alternatively, spin up a dedicated server with your OS of choice and full root access.
