Client-Side
Client-side scripting enables
interaction within a webpage.
The code required to process user-input is downloaded and compiled by the browser or plug-in. An example of a client-side interaction is a rollover (typically triggered when choosing a navigation option).
Client-side scripting languages include
JavaScript.
Server-Side
With server-side scripting, completing an activity involves
sending information to another computer (server) across the internet.
The server then runs a program that process the information and returns the results, typically a webpage.
Search engines use server-side processing. When a keyword is sent, a program on a server matches the word or phrase entered against an index of website content. (To complete the same search as a client-side process would require the browser to download the entire search engine program and index.)
Server-side scripting languages include
ASP and
PHP.
client-side interaction
- response to interaction may be more immediate (once the program code has been downloaded)
- services are secure (as no information is sent from the browser)
- reliant on the user having using a specific browser and/or plug-in on their computer
- affected by the processing speed of the user’s computer
server-side interaction
- complex processes are often more efficient (as the program and the associated resources are not downloaded to the browser)
- there are security considerations when sending sensitive information
- does not rely on the user having specific browser or plug-in
- affected by the processing speed of the host server
Refer more:
Server Side Verses Client Side[
^]
Client-Side vs. Server-Side Rendering[
^]
Submit an article or tip