0
Client side scripting is a script, (ex. Javascript, VB script), that is executed by the browser (i.e. Firefox, internet Explorer, Safari, Opera, etc.) that resides at the user computer.
Server side scripting, (ex. ASP.Net, ASP, JSP, PHP, Ruby, or others), is executed by the server (Web Server), and the page that is sent to the browser is produced by the serve-side scripting.
So when a server sends out a page, it executes server-side scripts, but does not execute client-side scripts. Once the browser receives the page, it executes the client-side scripts.
Server side scripting can connect to databases that reside on the web server or another server reachable from web server. Client side scripting cannot do that.
Server side scripting can access the file system that reside at the web server, client side cannot.
Server side scripting can access settings belong to Web server while client side cannot.
Client side scripting can access files and settings that are local at the user computer.
Client side scripting consumes cycles from user's computer not web server one, while server side scripting consumes cycles form web server one.
Still curious? Ask our experts.
Chat with our AI personalities
Blake
Rene
JudyServer-side scripting is a web technology that allows custom HTML to be delivered to a client machine where the code that generates the custom HTML is processed on the web server before the HTML is sent to the user's machine over the internet. Server-side scripting is a option for delivering customized HTML in contrast to client-side scripting, where the HTML is modified typically by java-script in the client's machine after the HTML and java are sent from the web server.
Server side scripting is when the users browser makes a request back to the server and the script creates the dynamic page based a number of conditions. Languages usually used are PHP or ASP. Example: On a website and the user clicks on the show the products link. The server then runs the PHP/ASP code to create a page by finding all the products in the data base. The page is created and sent back to the users browser for viewing. Client side scripting is when all the code is already on the users browser and the page alters based on the users input. Language is usually JavaScript. Example: A JavaScript drop down menu. The JavasScript alters how the menu is displayed but all the code is run locally while it is doing it.
Server side programming means that the code, whatever the programmer programmed, will run on the server. For example, the server might dynamically produce an HTML page, depending on user options (for example, when you do a search).
Client-side programming means that the program is run at the client. For example, you visit a Web page, a java applet, or flash page, is loaded in your browser, and the applet runs within your browser.
Server side scripting is a script language that runs on the server. PHP and ASP are the most popular. Because they run on the server, they are executed before the client even begins to download the file, making them significantly safer. Because of this, they are used to access databases and read files on the server.
Client side script are download as code by the browser, then executed once the download is finished. Client side code can be manipulated by the user, and is "sandboxed" so that it cannot access the user's file system.
Server side scripting refers to scripts written to access the server. Server side scripting is used in dynamic websites that are connected databases and websites that potentially run a store per say. Client side scripting is used to run programs on clients web browser. There is no need to access server side for lightweight programs. JavaScript is used for client side and PHP for server side.
The best client side scripting language is Javascript. All browsers support it, and it has a massive community behind it building things like frameworks and tools.
The best server-side scripting language is much more subjective. As a PHP programmer, I'm going to tell you it's PHP. Truth is, however, that depending on what you're trying to do and what other technologies you're trying to work with, ASP.NET, JSP, Ruby, Perl, or Python may very well be simpler to use and quicker.
All of them have their drawbacks, and all of them have their specific strengths. Generally, if you're starting a project, it's easier to look around and decide what your people are best at, rather than which language is the best.
A server-side scripting language is one that resides on the server. Whereas client-side scripting happens inside the users browser, after they've downloaded the code, server-side languages work before the file is sent from the server.
Server-side languages tend to deal with more "heavy lifting" than client side. They retrieve records from databases, maintain state over the stateless HTTP connection, and do a lot of things that require more security than JavaScript alone can provide. Because they reside on the server, these programs never have their source code exposed to the user. JavaScript source code must be available to the client by definition.
Some server-side languages are: C, PHP, Ruby, Python, JavaServer Pages, ColdFusion, ASP, and Perl.
Server-side scripting is programming that runs on the server. In the case of a site like Answers.com, things like searching the database and processing the posts of new answers are all server-side scripting.
Because server-side scripts are never accessed themselves by the client, they are significantly more secure than client-side scripts. In the case of JavaScript, for instance, a client-side script is available to the individual user in her browser. This means that the script can be manipulated, adjusted, or even circumvented at her end.
PHP, ASP, JSP, Ruby and Python are all popular server-side scripting languages. Because these languages have overtaken many of the older, compiled server-side programs, the entirety of the programming on the server is sometimes called server-side scripting, even though some of those languages (notably C) aren't script languages.)
Add your answer:
Earn +20 pts
What client side programming?
As far as web programming is concerned, client side programming is code that runs in the web browser, rather than the web server. JavaScript is an example of client side scripting because the code is sent to the browser, at which point it is executed. PHP is an example of server side scripting because the code is executed on the server, and the resulting code is sent to the browser and displayed.
What is the difference between client side scripting and server side scripting languages?
Best Practice : Use both The Cons of using one or the other : With client side validation only, if a user disables JavaScript, then no validation will occur. With server side validation only, there are more return trips to the server which in turns uses more resources and slows down the site when a client side script could have done the validation without the server. The Pros of having both : The data will always be validated, whether or not the client has JavaScript enabled or not. There will be less server strain with the client side validation. The client can fix form errors faster with instant client side notifications. The data will have a bit more integrity going through the dual validation process.
Where is JavaScript executed?
No. JavaScript is downloaded into the client's browser and executed there. With one caveat. Apache has a server-side JavaScript module that reached public experimental phase. It proved the concept, but saw little (if any) actual real world use.
What is client side usage in xml?
XML does not have the concept of client-side/server-side.
Why do you need different scripting for client and server side?
Partly because the available scripting languages are different: JavaScript runs primarily in the browser, which server side languages like PHP, JSP, Ruby on Rails etc. cannot do.Partly because the tasks are different: The server may do things like database lookup, reading/writing files and user authentication that would be either impossible or very insecure to do in a browser.That said, there are a number of tasks that can be done either on the client or the server, like generating the HTML for the page.There are also a couple of tasks that are commonly done both places, like form validation - on the client to give quick feedback and on the server to ensure that what is submitted is actually safe and valid. (An attacker could easily skip any browser validation and submit illegal values.)If you wish to share as much code between client and server as you can, server side JavaScript exists, so it is possible to use the same language both places. There will still be different scripting, as there are tasks that can only be done on the server.See related link for some server side JavaScript options.
