This page allows you to examine the variables generated by the Edit Filter for an individual change.

Variables generated for this change

VariableValue
Name of the user account (user_name)
'37.237.5.214'
Page ID (page_id)
29288
Page namespace (page_namespace)
0
Page title without namespace (page_title)
'Server-side scripting'
Full page title (page_prefixedtitle)
'Server-side scripting'
Action (action)
'edit'
Edit summary/reason (summary)
'/* History */'
Whether or not the edit is marked as minor (no longer in use) (minor_edit)
false
Old page wikitext, before the edit (old_wikitext)
'{{Expert-subject|Technology|reason=unfocused, scattered, unnecessary details|date=April 2012}} {{Refimprove|date=October 2008}} {{See also2|[[Dynamic web page#Server-side scripting|Dynamic web pages: Server-side scripting]]}} [[File:Scheme dynamic page en.svg|thumb|right|600px|Dynamic web page: example of server-side scripting (PHP and MySQL).]] '''Server-side scripting''' is a technique used in [[website design]] which involves embedding [[Scripting language|script]]s in an [[HTML]] [[source code]] which results in a user's (client's) request to the server website being handled by a script running server-side before the server responds to the client's request. The scripts can be written in any of a number of server-side scripting languages available (see below). Server-side scripting differs from [[client-side scripting]] where embedded scripts, such as [[JavaScript]], are run client-side in the [[web browser]]. Server-side scripting is usually used to provide an interface and to limit client access to proprietary databases or other data sources. These scripts may assemble client characteristics for use in customizing the response based on those characteristics, the user's requirements, access rights, etc. Server-side scripting also enables the website owner to reduce user access to the source code of server-side scripts which may be proprietary and valuable in itself. The down-side to the use of server-side scripting is that the server website computer needs to provide most of the computing resources before sending a page to the client computer for display via its web browser. When the server serves data in a commonly used manner, for example according to the [[Hypertext Transfer Protocol|HTTP]] or [[File Transfer Protocol|FTP]] [[Protocol (computing)|protocols]], users may have their choice of a number of client programs (most modern web browsers can request and receive data using both of those protocols). In the case of more specialized applications, programmers may write their own server, client, and communications protocol, that can only be used with one another. Programs that run on a user's local computer without ever sending or receiving data over a network are not considered clients, and so the operations of such programs would not be considered client-side operations. == History == Server-side scripting was first used in early 1995 by [[Fred DuFresne]] while developing the first web site for Boston, MA television station [[WCVB-TV|WCVB]]. The technology is described in [http://patft.uspto.gov/netacgi/nph-Parser?Sect2=PTO1&Sect2=HITOFF&p=1&u=/netahtml/PTO/search-bool.html&r=1&f=G&l=50&d=PALL&RefSrch=yes&Query=PN/5835712 US patent 5835712]. The patent was issued in 1998 and is now owned by [[Open Invention Network]] (OIN). In 2010 OIN named Fred DuFresne a [http://www.openinventionnetwork.com/press_release06_07_11.php "Distinguished Inventor"] for his work on server-side scripting. == Explanation == In the earlier days of the web, server-side scripting was almost exclusively performed by using a combination of [[C (programming language)|C]] programs, [[Perl]] scripts, and [[shell script]]s using the [[Common Gateway Interface]] (CGI). Those scripts were executed by the [[operating system]], and the results were served back by the web server. Many modern web servers can directly execute on-line scripting languages such as [[Active Server Pages|ASP]] and [[PHP]] either by the web server itself or via extension modules (e.g. [[mod_perl]] or [[mod_php]]) to the web server. For example, [[WebDNA]] includes its own embedded database system. Either form of scripting (i.e., CGI or direct execution) can be used to build up complex multi-page sites, but direct execution usually results in lower overhead due to the lack of calls to external interpreters. Dynamic websites sometimes use custom web application servers, for example the [[Python (programming language)|Python]] "Base HTTP Server" library, although some may not consider this to be server-side scripting. When designing using dynamic web-based scripting technics, like classic ASP or PHP, developers must have a keen understanding of the logical, temporal, and physical separation between the client and the server. For a user's action to trigger the execution of server-side code, for example, a developer working with classic ASP must explicitly cause the user's browser to make a request back to the web server. Creating such interactions can easily consume much development time and lead to unreadable code. ==Server-side scripting languages== <!-- please don't list languages like Python, Perl, and Ruby here, see [[Talk:Server-side_scripting#Too_many_languages]] --> There are a number of server-side scripting languages available, including: * [[Active Server Pages|ASP]] (*.asp) * [[ActiveVFP]] (*.avfp) * [[ASP.NET]] (*.aspx) * [[C (programming language)|C]] via [[Common Gateway Interface|CGI]] (*.c, *.csp) * [[ColdFusion Markup Language]] (*.cfm) * [[Java (programming language)|Java]] via [[JavaServer Pages]] (*.jsp) * [[JavaScript]] using [[Server-side JavaScript]] (*.ssjs, *.js) * [[Lua (programming language)|Lua]] (*.lp *.op) * [[Perl CGI]] (*.cgi, *.ipl, *.pl) * [[PHP]] (*.php) - Open Source Scripting * [[Python_(programming_language)|Python]], e.g. via [[Django_(Web_framework)|Django]] (*.py) * [[Ruby programming language|Ruby]], e.g. [[Ruby on Rails]] (*.rb, *.rbw) * [[SMX (computer language)|SMX]] (*.smx) * [[Lasso (programming language)|Lasso]] (*.lasso) * [[WebDNA]] (*.dna,*.tpl) * [[OpenEdge Advanced Business Language|Progress WebSpeed]] (*.r,*.w) ==See also== * [[Content management system|Content management system (CMS)]] * [[Web development]] * [[Server-side JavaScript]] * [[Client-side scripting]] * [[Server Side Includes]] * [[Edge Side Includes]] ==External links== * {{dmoz|Computers/Programming/Internet/Server_Side_Scripting}} {{DEFAULTSORT:Server-Side Scripting}} [[Category:Scripting languages]] [[cs:Skriptování na straně serveru]] [[de:Server Side Scripting]] [[es:Script del lado del servidor]] [[fr:Langage serveur]] [[ko:서버 사이드 스크립트 언어]] [[mk:Скриптирање на опслужувачка страна]] [[nl:Server-side scripting]] [[ja:サーバーサイド・スクリプト]] [[pt:Linguagem server-side]] [[th:เซิร์ฟเวอร์-ไซด์ สคริปต์]]'
New page wikitext, after the edit (new_wikitext)
'{{Expert-subject|Technology|reason=unfocused, scattered, unnecessary details|date=April 2012}} {{Refimprove|date=October 2008}} {{See also2|[[Dynamic web page#Server-side scripting|Dynamic web pages: Server-side scripting]]}} [[File:Scheme dynamic page en.svg|thumb|right|600px|Dynamic web page: example of server-side scripting (PHP and MySQL).]] '''Server-side scripting''' is a technique used in [[website design]] which involves embedding [[Scripting language|script]]s in an [[HTML]] [[source code]] which results in a user's (client's) request to the server website being handled by a script running server-side before the server responds to the client's request. The scripts can be written in any of a number of server-side scripting languages available (see below). Server-side scripting differs from [[client-side scripting]] where embedded scripts, such as [[JavaScript]], are run client-side in the [[web browser]]. Server-side scripting is usually used to provide an interface and to limit client access to proprietary databases or other data sources. These scripts may assemble client characteristics for use in customizing the response based on those characteristics, the user's requirements, access rights, etc. Server-side scripting also enables the website owner to reduce user access to the source code of server-side scripts which may be proprietary and valuable in itself. The down-side to the use of server-side scripting is that the server website computer needs to provide most of the computing resources before sending a page to the client computer for display via its web browser. When the server serves data in a commonly used manner, for example according to the [[Hypertext Transfer Protocol|HTTP]] or [[File Transfer Protocol|FTP]] [[Protocol (computing)|protocols]], users may have their choice of a number of client programs (most modern web browsers can request and receive data using both of those protocols). In the case of more specialized applications, programmers may write their own server, client, and communications protocol, that can only be used with one another. Programs that run on a user's local computer without ever sending or receiving data over a network are not considered clients, and so the operations of such programs would not be considered client-side operations. == History == Server-side scripting was first used in early 1995 by [[Fred DuFresne]] while developing the first web site for Boston, MA television station [[WCVB-TV|WCVB]]. The technology is described in [http://patft.uspto.gov/netacgi/nph-Parser?Sect2=PTO1&Sect2=HITOFF&p=1&u=/netahtml/PTO/search-bool.html&r=1&f=G&l=50&d=PALL&RefSrch=yes&Query=PN/5835712 US patent 5835712]. The patent was issued in 1998 and is now owned by [[Open Invention Network]] (OIN). In 2010 OIN named Fred DuFresne a [http://www.openinventionnetwork.com/press_release06_07_11.php "Distinguished Inventor"] for his work on server-side scripting. firas layth == Explanation == In the earlier days of the web, server-side scripting was almost exclusively performed by using a combination of [[C (programming language)|C]] programs, [[Perl]] scripts, and [[shell script]]s using the [[Common Gateway Interface]] (CGI). Those scripts were executed by the [[operating system]], and the results were served back by the web server. Many modern web servers can directly execute on-line scripting languages such as [[Active Server Pages|ASP]] and [[PHP]] either by the web server itself or via extension modules (e.g. [[mod_perl]] or [[mod_php]]) to the web server. For example, [[WebDNA]] includes its own embedded database system. Either form of scripting (i.e., CGI or direct execution) can be used to build up complex multi-page sites, but direct execution usually results in lower overhead due to the lack of calls to external interpreters. Dynamic websites sometimes use custom web application servers, for example the [[Python (programming language)|Python]] "Base HTTP Server" library, although some may not consider this to be server-side scripting. When designing using dynamic web-based scripting technics, like classic ASP or PHP, developers must have a keen understanding of the logical, temporal, and physical separation between the client and the server. For a user's action to trigger the execution of server-side code, for example, a developer working with classic ASP must explicitly cause the user's browser to make a request back to the web server. Creating such interactions can easily consume much development time and lead to unreadable code. ==Server-side scripting languages== <!-- please don't list languages like Python, Perl, and Ruby here, see [[Talk:Server-side_scripting#Too_many_languages]] --> There are a number of server-side scripting languages available, including: * [[Active Server Pages|ASP]] (*.asp) * [[ActiveVFP]] (*.avfp) * [[ASP.NET]] (*.aspx) * [[C (programming language)|C]] via [[Common Gateway Interface|CGI]] (*.c, *.csp) * [[ColdFusion Markup Language]] (*.cfm) * [[Java (programming language)|Java]] via [[JavaServer Pages]] (*.jsp) * [[JavaScript]] using [[Server-side JavaScript]] (*.ssjs, *.js) * [[Lua (programming language)|Lua]] (*.lp *.op) * [[Perl CGI]] (*.cgi, *.ipl, *.pl) * [[PHP]] (*.php) - Open Source Scripting * [[Python_(programming_language)|Python]], e.g. via [[Django_(Web_framework)|Django]] (*.py) * [[Ruby programming language|Ruby]], e.g. [[Ruby on Rails]] (*.rb, *.rbw) * [[SMX (computer language)|SMX]] (*.smx) * [[Lasso (programming language)|Lasso]] (*.lasso) * [[WebDNA]] (*.dna,*.tpl) * [[OpenEdge Advanced Business Language|Progress WebSpeed]] (*.r,*.w) ==See also== * [[Content management system|Content management system (CMS)]] * [[Web development]] * [[Server-side JavaScript]] * [[Client-side scripting]] * [[Server Side Includes]] * [[Edge Side Includes]] ==External links== * {{dmoz|Computers/Programming/Internet/Server_Side_Scripting}} {{DEFAULTSORT:Server-Side Scripting}} [[Category:Scripting languages]] [[cs:Skriptování na straně serveru]] [[de:Server Side Scripting]] [[es:Script del lado del servidor]] [[fr:Langage serveur]] [[ko:서버 사이드 스크립트 언어]] [[mk:Скриптирање на опслужувачка страна]] [[nl:Server-side scripting]] [[ja:サーバーサイド・スクリプト]] [[pt:Linguagem server-side]] [[th:เซิร์ฟเวอร์-ไซด์ สคริปต์]]'
Whether or not the change was made through a Tor exit node (tor_exit_node)
0
Unix timestamp of change (timestamp)
1361036267