Written by Segue Technologieson February 11, 2013
Client-side scripting, like JavaScript, can be embedded into the page on the client’s browser. This script will allow the client’s browser to alleviate some of the burden on your web server when running a web application. Client-side scripting is source code that is executed on the client’s browser instead of the web-server, and allows for the creation of faster and more responsive web applications.
What is the difference between a web application and a traditional windows application? A great example of a windows application is Microsoft Office, which is installed on a client’s workstation; other than calls to the database server to save and retrieve data, all the source code and assemblies are run locally. In fact, it is a requirement that a windows application be installed on the client’s workstation. Web applications, on the other hand, don’t need to be installed on individual workstations. An internet connection and a browser like Internet Explorer, Firefox or Google Chrome is all you need. However, the majority of the processing will not take place on the client’s browser, but on a web server at some other location.
The Need for Client-Side Scripting
As web applications become more and more powerful and sophisticated, it is expected that they function and act just like a windows application. The basic architecture for a web application is that most of the source code and assemblies reside and are processed on a web server. The sole task of a web server is to accept incoming HTTP requests and to return the requested resource in an HTTP response. There is never a continuous live connection between the client’s browser and the web server. Web pages will always be in the form of HTML.
PostBack is the name given to the process of submitting an ASP.NET page to the server for processing. Every time a PostBack happens, the HTML page is sent to the web server. The server loads the page, processes events and renders the new HTML back to the client. On a PostBack, the entire HTML is refreshed.
For large and complex web-applications that store a large amount of View state, this can be very time consuming for the client. This will become a huge problem for a web server with limited resources like memory and bandwidth.
Web applications will usually embed view state in the HTML page. Quoting Microsoft, “Microsoft® ASP.NET view state, in a nutshell, is the technique used by an ASP.NET Web page to persist changes to the state of a Web Form across postbacks.” View state allows the state of objects to be stored in a hidden field on the page. View state is transported to the client and back to the server, and is not stored on the server or any other external source. View state is used to retain the state of server-side objects between postbacks and will become very large for large applications and pages.
Client-side scripting (embedded scripts) is code that exists inside the client’s HTML page. This code will be processed on the client machine and the HTML page will NOT perform a PostBack to the web-server. Traditionally, client-side scripting is used for page navigation, data validation and formatting. The language used in this scripting is JavaScript. JavaScript is compatible and is able to run on any internet browser.
The two main benefits of client-side scripting are:
- The user’s actions will result in an immediate response because they don’t require a trip to the server.
- Fewer resources are used and needed on the web-server.
Ajax and jQuery
The two huge advances in client-side scripting are Ajax and jQuery. Ajax is not a tool or a programing language, but a concept. The concept is to call the server directly from the client without doing a PostBack. The main advantage of Ajax is to save and retrieve data from a database, bypassing the web server, which is known as a CallBack. Web Services will be created to do database operations. Your client-side scripts will call these web-services asynchronously.
However, there are disadvantages to client-side scripting. One disadvantage of client-side scripting is that JavaScript is not as easy to write as the traditional server-side languages like C# and VB.Net. Also, languages like C# and VB.Net have access to the .Net Framework. jQuery is a multi-browser JavaScript library designed to simplify client-side scripting and serves as is a wrapper around JavaScript. jQuery is free open source software.
According to their website, jQuery is defined as, “a fast, small, and feature-rich JavaScript library. It makes things like HTML document traversal and manipulation, event handling, animation, and Ajax much simpler with an easy-to-use API that works across a multitude of browsers. With a combination of versatility and extensibility, jQuery has changed the way that millions of people write JavaScript.”
As web applications become larger and more complex, combined with the increasing popularity of mobile applications that run on smart phones and other mobile devices, the need for client-side scripting, Ajax and jQuery will continue to grow.
FAQs
The two main benefits of client-side scripting are: The user's actions will result in an immediate response because they don't require a trip to the server. Fewer resources are used and needed on the web-server.
What are the benefits of client-side scripting? ›
Improved User Experience: Client-side scripting provides a more interactive and dynamic user experience with features such as form validation, live updates, and animations.
How does client-side scripting enhance web pages to provide an improved client internet experience? ›
Client side processing involves carrying out computational tasks within the user's browser using scripting languages like JavaScript. It enables interactive user interfaces, reduces server load, and improves performance through faster loading times.
What are two advantages to the user when a website uses client-side processing? ›
Client-side web application programming languages like JavaScript offer benefits such as enhanced user experience through dynamic and interactive interfaces, reduced server load by handling tasks locally, and cross-platform compatibility for consistent performance across devices and browsers.
How to improve the performance of client server applications? ›
The following is a suggested guideline for client/server operations: Communicate with the server only when necessary, and in as few data transmissions as possible. Opening a file and reading one record at a time often results in problems for client-server projects and tools.
How does client-side scripting affect website performance? ›
Similar to JavaScript, you can add a Client-side script to your web page that the client can interact with through a web browser. This short code will enable the browser to reduce the load on your server. Essentially, the script eases the load of the web page allowing the user to run a web application smoothly.
What are the pros and cons of client-side and server-side? ›
Client-side processes are executed on the user's device after the web application is delivered. Server-side processes have more access to resources and are more secure, while client-side processes have less access to resources and are potentially less secure.
What is the main feature of client-side scripting? ›
Client-side scripting simply means running scripts, such as JavaScript, on the client device, usually within a browser. All kinds of scripts can run on the client side if they are written in JavaScript, because JavaScript is universally supported.
What is the main goal of adding client script to a web page? ›
Client scripts allow the system to run JavaScript on the client (web browser) when client-based events occur, such as when a form loads, after form submission, or when a field changes value. Use client scripts to configure forms, form fields, and field values while the user is using the form.
What are the disadvantages of client-side scripting in web technology? ›
The biggest drawback to client-side scripting is it's not secure because the code is transmitted in the form of a message to the client and, therefore, accessible to it when the user checks the sources of his website page. In other words, the code is typically visible.
JavaScript is a client-side script, meaning the browser processes the code instead of the web server. Client-side scripts are commonly used when we want to validate data before sending it to the web server, adjusting the interface in response to user feedback, and for implementing other advanced features.
What are the benefits of working client side? ›
Client-side is comparably calmer. And it makes sense. You're working with one brand or company, the team is likely to be much smaller and you are predominantly 'the client', or working next door to the decision maker, which can make things, like the approval process, slightly easier (most of the time anyway!).
When should client side processing be used? ›
Client side processing is better for tasks that require immediate user feedback, real-time interactions, dynamic user interfaces, or data manipulation within the browser.
How to enhance application performance? ›
How to Improve Application Performance
- Tip 1: Monitor all transactions for all users. ...
- Tip 2: Monitor what you don't control. ...
- Tip 3: Understand the end user experience. ...
- Tip 4: Incorporate APM into your change management processes. ...
- Tip 5: Shift left with regards to APM.
Our 5 essential tips can help you tune your server to fix or avoid common problems, like bottlenecks and overutilization, that cause disruptive downtime.
- 1) Select the Right Application for Server Optimization.
- 2) Setup a Quick Reverse Proxy.
- 3) Enable Caching.
- 4) Defragment Database Tables & Optimize Server Settings.
One way to mitigate the negative effects of client-side rendering on loading speed and performance is to use techniques such as lazy loading, which allows the website to load only the assets that are needed at the time, rather than loading all assets at once.
What are the benefits of working client-side? ›
Client-side is comparably calmer. And it makes sense. You're working with one brand or company, the team is likely to be much smaller and you are predominantly 'the client', or working next door to the decision maker, which can make things, like the approval process, slightly easier (most of the time anyway!).
Why is SSR important? ›
With SSR, the client doesn't need to wait for JavaScript or CSS files to load. Instead, the web page is fully rendered and filled with the necessary content. This leads to a better user experience because web visitors won't encounter a blank screen while waiting for the required code to load.
What are the pros and cons of client-side state management techniques? ›
Client-side State Management
This technique stores data on the client's browser instead of using the server resources. The major benefit with this technique is better scalability. However, as the data is stored on the client's end, it is less secure and cannot be used to store any kind of sensitive data.
