Content deleted Content added
No edit summary |
|||
Line 7:
By viewing the file that contains the script, users may be able to see its [[source code]]. Many web authors learn how to write client-side scripts partly by examining the source code for other authors' scripts.
In contrast, [[server-side scripting|server-side scripts]], written in languages such as [[PHP]], [[ASP.NET]], [[Java (programming language)|Java]], [[Adobe ColdFusion]], [[Perl]], [[Ruby (programming language)|Ruby]], [[Go (programming language)|Go]], [[Python (programming language)|Python]], and [[JavaScript#Server-side JavaScript|server-side JavaScript]],<ref>{{cite web|title=Web technology survey: Usage of server-side programming languages for websites|url=http://w3techs.com/technologies/overview/programming_language/all|publisher=W3Techs.com|accessdate=9 December 2013}}</ref> are executed by the web server when the user requests a document. They produce output in a format understandable by web browsers (usually HTML), which is then sent to the user's computer. The user cannot see the script's source code (unless the author publishes the code separately), and may not even be aware that a script was executed. Documents produced by server-side scripts may, in turn, contain client-side scripts.
Server-side scripts require that their language's [[Interpreter (computing)|interpreter]] be installed on the server, and produce the same output regardless of the client's browser, [[operating system]], or other system details. Client-side scripts do not require additional software on the server (making them popular with authors who lack administrative access to their servers); however, they do require that the user's web browser understands the scripting language in which they are written. It is therefore impractical for an author to write scripts in a language that is not supported by popular web browsers.
| |||