Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #11697
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Newsgroups | comp.lang.php |
| Subject | Re: server-side vs.client-side |
| Date | 2013-11-02 01:24 +0100 |
| Message-ID | <52744623.1080001@arnowelzel.de> (permalink) |
| References | (10 earlier) <52714a1c$0$6557$9b4e6d93@newsspool4.arcor-online.net> <l4rksd$7ap$2@dont-email.me> <527163e4$0$6563$9b4e6d93@newsspool4.arcor-online.net> <52721771.6090201@arnowelzel.de> <vilain-283EF4.09532801112013@news.individual.net> |
Michael Vilain, 2013-11-01 17:53: > In article <52721771.6090201@arnowelzel.de>, > Arno Welzel <usenet@arnowelzel.de> wrote: > >> Christoph Michael Becker, 2013-10-30 20:54: >> >>> Jerry Stuckle wrote: >>> >>>> One question - since both you and Thomas seem to be from Germany, and >>>> have the same misunderstanding of the word "normally", what does >>>> "normally" translate to in German? What does it mean? >>> >>> In Germany it is "normalerweise"/"üblicherweise", what means as much >>> usually. Anyway, a misunderstanding of the term "normally" is not the >>> problem here for me. In my opinion, it is correct to state: "PHP is >>> normally (usually, most often etc.) used on a server (for server-side >>> programming)." >>> >>> It is as well correct to state: "No programming language is normally >>> either server-side or client-side." Otherwise it would mean, that there >>> are programming languages that couldn't be used outside of a >>> client-server context. >> >> Exactly *this* is the wrong assumption, what "normally" means in this >> context. It does *NOT* mean that a language can *never* be used in other >> ways - it only says that is the the most common use of it. > > I've never seen javascript run on anything but a browser. Unless > someone's developed a non-browser version, I personally consider it a > client-side scripting language. It's meant to control a browser and > nothing else, which is the client for web pages. JFTR: see Node.js - this is "server side" JavaScript: <http://nodejs.org/about/> But generally you're right - the more common use of JavaScript is "client side" and originally JavaScript has been created just for this purpose, even though ECMAScript is not limited to this and can virtually be found anywhere (even as scripting language for Office applications or for command line tools). Therefore I would also not call JavaScript a "normally server side language" - using it on a server is just another option. > php is not intended to run on the browser. It runs on the server that > the browser talks to. It can run as part of the web-server or from the > command line. Same for perl, Java, python, ruby, or C. To me, that > makes them server-side programming languages. I even don't know any PHP runtime for browsers. > I don't know if that matches other's definitions of server-side vs. > client-side, but that's my definition. I would define "server side" in the context of PHP as "will usually not be executed by a user agent". If the "server" is a public web server or just the box sitting under your desktop does not make a big difference. -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de
Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
checking for audio playing ??? richard <noreply@example.com> - 2013-10-27 10:58 -0400
Re: checking for audio playing ??? Christoph Michael Becker <cmbecker69@arcor.de> - 2013-10-27 16:45 +0100
Re: checking for audio playing ??? richard <noreply@example.com> - 2013-10-27 12:01 -0400
Re: checking for audio playing ??? Denis McMahon <denismfmcmahon@gmail.com> - 2013-10-27 17:53 +0000
Re: checking for audio playing ??? richard <noreply@example.com> - 2013-10-27 14:24 -0400
Re: checking for audio playing ??? Doug Miller <doug_at_milmac_dot_com@example.com> - 2013-10-27 18:38 +0000
Re: checking for audio playing ??? Richard Damon <Richard@Damon-Family.org> - 2013-10-27 14:43 -0400
Re: checking for audio playing ??? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-10-28 03:22 +0100
Re: checking for audio playing ??? Jerry Stuckle <jstucklex@attglobal.net> - 2013-10-28 05:49 -0400
Re: checking for audio playing ??? Richard Damon <Richard@Damon-Family.org> - 2013-10-28 08:11 -0400
Re: checking for audio playing ??? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-10-28 14:37 +0100
Re: checking for audio playing ??? "Beauregard T. Shagnasty" <a.nony.mous@example.invalid> - 2013-10-28 13:49 +0000
Re: checking for audio playing ??? Jerry Stuckle <jstucklex@attglobal.net> - 2013-10-28 10:01 -0400
Re: checking for audio playing ??? Scott Johnson <noonehome@chalupasworld.com> - 2013-10-28 11:36 -0700
Re: checking for audio playing ??? Richard Damon <Richard@Damon-Family.org> - 2013-10-28 21:29 -0400
Re: checking for audio playing ??? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-10-29 12:18 +0100
cr Richard Damon <Richard@Damon-Family.org> - 2013-10-31 23:21 -0400
Re: cr Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-03 15:29 +0100
Re: cr Jerry Stuckle <jstucklex@attglobal.net> - 2013-11-03 09:34 -0500
Re: cr Richard Damon <Richard@Damon-Family.org> - 2013-11-03 15:18 -0500
Re: checking for audio playing ??? Arno Welzel <usenet@arnowelzel.de> - 2013-10-29 20:12 +0100
Re: checking for audio playing ??? Doug Miller <doug_at_milmac_dot_com@example.com> - 2013-10-29 20:21 +0000
Re: checking for audio playing ??? Arno Welzel <usenet@arnowelzel.de> - 2013-10-29 20:10 +0100
server-side vs.client-side (was: checking for audio playing ???) Christoph Michael Becker <cmbecker69@arcor.de> - 2013-10-29 21:45 +0100
Re: server-side vs.client-side Jerry Stuckle <jstucklex@attglobal.net> - 2013-10-29 20:54 -0400
Re: server-side vs.client-side Christoph Michael Becker <cmbecker69@arcor.de> - 2013-10-30 03:18 +0100
Re: server-side vs.client-side Jerry Stuckle <jstucklex@attglobal.net> - 2013-10-29 22:31 -0400
Re: server-side vs.client-side Arno Welzel <usenet@arnowelzel.de> - 2013-10-30 09:20 +0100
Re: server-side vs.client-side Christoph Michael Becker <cmbecker69@arcor.de> - 2013-10-30 19:04 +0100
Re: server-side vs.client-side Jerry Stuckle <jstucklex@attglobal.net> - 2013-10-30 14:58 -0400
Re: server-side vs.client-side Christoph Michael Becker <cmbecker69@arcor.de> - 2013-10-30 20:54 +0100
Re: server-side vs.client-side Jerry Stuckle <jstucklex@attglobal.net> - 2013-10-30 16:21 -0400
Re: server-side vs.client-side Christoph Michael Becker <cmbecker69@arcor.de> - 2013-10-30 21:55 +0100
Re: server-side vs.client-side Jerry Stuckle <jstucklex@attglobal.net> - 2013-10-30 17:07 -0400
Re: server-side vs.client-side Arno Welzel <usenet@arnowelzel.de> - 2013-10-31 09:40 +0100
Re: server-side vs.client-side Christoph Michael Becker <cmbecker69@arcor.de> - 2013-10-31 23:03 +0100
Re: server-side vs.client-side Jerry Stuckle <jstucklex@attglobal.net> - 2013-10-31 20:38 -0400
Re: server-side vs.client-side Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-02 17:57 +0100
Re: server-side vs.client-side Arno Welzel <usenet@arnowelzel.de> - 2013-11-02 19:36 +0100
Re: server-side vs.client-side The Natural Philosopher <tnp@invalid.invalid> - 2013-11-02 18:44 +0000
Re: server-side vs.client-side Denis McMahon <denismfmcmahon@gmail.com> - 2013-11-03 00:28 +0000
Re: server-side vs.client-side Doug Miller <doug_at_milmac_dot_com@example.com> - 2013-11-02 19:01 +0000
Re: server-side vs.client-side Jerry Stuckle <jstucklex@attglobal.net> - 2013-11-02 21:40 -0400
Re: server-side vs.client-side Michael Vilain <vilain@NOspamcop.net> - 2013-11-01 09:53 -0700
Re: server-side vs.client-side Jerry Stuckle <jstucklex@attglobal.net> - 2013-11-01 13:53 -0400
Re: server-side vs.client-side Tim Streater <timstreater@greenbee.net> - 2013-11-01 21:10 +0000
Re: server-side vs.client-side The Natural Philosopher <tnp@invalid.invalid> - 2013-11-01 22:25 +0000
Re: server-side vs.client-side Tim Streater <timstreater@greenbee.net> - 2013-11-01 22:29 +0000
Re: server-side vs.client-side Jerry Stuckle <jstucklex@attglobal.net> - 2013-11-01 20:37 -0400
Re: server-side vs.client-side Arno Welzel <usenet@arnowelzel.de> - 2013-11-02 01:26 +0100
Re: server-side vs.client-side The Natural Philosopher <tnp@invalid.invalid> - 2013-11-01 18:37 +0000
Re: server-side vs.client-side Stefan+Usenet@Froehlich.Priv.at (Stefan Froehlich) - 2013-11-01 19:19 +0000
Re: server-side vs.client-side Arno Welzel <usenet@arnowelzel.de> - 2013-11-02 01:24 +0100
Re: server-side vs.client-side Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-02 17:46 +0100
Re: server-side vs.client-side Richard Damon <Richard@Damon-Family.org> - 2013-11-02 15:41 -0400
Re: server-side vs.client-side Tim Streater <timstreater@greenbee.net> - 2013-11-02 21:37 +0000
Re: server-side vs.client-side Arno Welzel <usenet@arnowelzel.de> - 2013-11-03 10:48 +0100
Re: server-side vs.client-side Tim Streater <timstreater@greenbee.net> - 2013-11-03 10:28 +0000
Re: server-side vs.client-side Arno Welzel <usenet@arnowelzel.de> - 2013-11-05 11:15 +0100
Re: server-side vs.client-side Tim Streater <timstreater@greenbee.net> - 2013-11-05 12:47 +0000
Re: server-side vs.client-side Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-03 14:16 +0100
Re: server-side vs.client-side Tim Streater <timstreater@greenbee.net> - 2013-11-03 16:00 +0000
Re: server-side vs.client-side Chuck Anderson <cycletourist@invalid.invalid> - 2013-11-03 14:52 -0700
Re: server-side vs.client-side Chuck Anderson <cycletourist@invalid.invalid> - 2013-11-03 23:19 -0700
Re: server-side vs.client-side Tim Streater <timstreater@greenbee.net> - 2013-11-04 18:02 +0000
Re: server-side vs.client-side Arno Welzel <usenet@arnowelzel.de> - 2013-10-30 09:09 +0100
Re: checking for audio playing ??? Denis McMahon <denismfmcmahon@gmail.com> - 2013-10-28 15:23 +0000
Re: checking for audio playing ??? The Natural Philosopher <tnp@invalid.invalid> - 2013-10-28 16:56 +0000
Re: checking for audio playing ??? Doug Miller <doug_at_milmac_dot_com@example.com> - 2013-10-27 18:22 +0000
Re: checking for audio playing ??? Arno Welzel <usenet@arnowelzel.de> - 2013-10-28 20:02 +0100
csiph-web