{"id":9586,"date":"2014-09-14T05:09:28","date_gmt":"2014-09-13T19:09:28","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/wordpress\/?p=9586"},"modified":"2014-09-14T05:09:28","modified_gmt":"2014-09-13T19:09:28","slug":"php-modes-of-use-follow-up-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/php-modes-of-use-follow-up-tutorial\/","title":{"rendered":"PHP Modes of Use Follow Up Tutorial"},"content":{"rendered":"
\"PHP<\/a>

PHP Modes of Use Follow Up Tutorial<\/p><\/div>\n

PHP<\/a> is a very flexible programming language, as we saw during the previous PHP Modes of Use Primer Tutorial<\/a> as shown below, where, below, we quote from this blog post largely, and highlight ideas that do not always work in orange<\/font> and updated ideas to help “shore up” the ideas in green<\/font>. It is probably best known as a server-side language called by a web browser using the http transport layer (ie. web browsing, or “surfing the net”). Let’s list three modes of use of PHP below:<\/p>\n

    \n
  1. Via http transport layer (ie. web browsing, or “surfing the net”) in an Internet<\/a> mode of use (eg: http:\/\/localhost:8888\/more_in_tra_ter_net.php?SERVER_NAME=localhost) in address bar of a web browser<\/li>\n
  2. Via curl<\/a> in an Internet mode of use (eg. curl http:\/\/localhost:8888\/more_in_tra_ter_net.php?SERVER_NAME=localhost) at Linux or unix or Windows command line to default output (and you can redirect as required via > outfile<\/i> or >> outfile<\/i> or 2> errfile<\/i> or 2>> errfile<\/i>)<\/li>\n
  3. Via command line PHP in Linux or unix or Windows command line in a command or Intranet<\/a> mode of use (eg. php more_in_tra_ter_net.php SERVER_NAME=localhost) at a Linux or unix or Windows command line (where the PHP code has been placed, in our example (ie. it is not a URL, but is a file specification of your (Intranet) server)) to default output (or you can redirect as required via > outfile<\/i> or >> outfile<\/i> or 2> errfile<\/i> or 2>> errfile<\/i>)<\/li>\n<\/ol>\n

    Does it matter how the PHP is accessed? Well, yes, it does … sometimes, but not if the code is restricted to a particular mode of usage (but part of what this tutorial is about is to get across how flexible and powerful PHP can be). With the last option above, lots of $_SERVER[]<\/a> variables are undefined, for example.<\/p>\n

      \n
    1. $_SERVER[‘HTTP_COOKIE’] is defined, unlike with curl usage (this seems to be a possibility as a way to detect curl usage).<\/font> (see green bits below, because $_SERVER[‘HTTP_COOKIE’] became undefined on MAMP by the passing of time between the two tutorials, so we looked to find another way to tell the difference between web surfing mode and curl mode of PHP usage\/access).<\/font> Most $_SERVER[] variables are defined, but $argv[] array is not.<\/li>\n
    2. $_SERVER[‘HTTP_COOKIE’] is undefined, … as a follow up idea here today, brought on by the fact that here with the local MAMP server we are testing on, as with the old live link from the rjmprogramming.com.au web server (sometimes (though not just this minute of writing) … clearly, with all this you may need more of your own research into the behaviour of the PHP $_SERVER[] array, as per links below) in tutorial below $_SERVER[‘HTTP_COOKIE’] can become undefined for both web surfing and curl modes of use (and so becomes a less than effective means of detecting curl supervision, in the PHP code) over time (am not aware, exactly when this happened) … in any case, another approach can be to examine $_SERVER[‘HTTP_USER_AGENT’] for the existence of the word “curl”<\/i> at its beginning to test for the curl<\/i> mode of use … again, this can be an effective test from a HTTP friendly client, but this may not be a perfect test or solution because $_SERVER[‘HTTP_USER_AGENT’] can be manipulated (ref: link<\/a>)<\/font>, but a lot of the rest of $_SERVER[] variables are as above.<\/li>\n
    3. Lots of $_SERVER[] variables are undefined, with the exception of $_SERVER[‘SCRIPT_FILENAME’] which may help you with Intranet application usage. You cannot enter $_GET[] arguments (on the command line (ie. you will get a syntax error if you try)) so these are undefined, but $argv[] array can be used in that awkward way shown, so that $argv[1] can be arranged to be a lot like $_SERVER[‘QUERY_STRING’] (ie. the bits after ? in a URL).<\/li>\n<\/ol>\n

      So, maybe you have the one mode of use in mind, but you need to think a bit to support all the modes of use, if they are all to have a role with the PHP you write, because, despite these differences it is good to use $_SERVER[] and $_GET[] and $_POST[] and $_SESSION[] and $argv[] and whatever else in terms of variable information PHP offers in terms of attempting to write generic code.<\/p>\n

      Hope you get something out of today’s discussion<\/a> of our Mac OS X MAMP Apache local Web server environment example (hence the http:\/\/localhost:8888\/<\/i> you see in the URLs above), but please bear in mind that there would be other modes of use once you think of other client HTML element ways of accessing PHP (all a lot like the “web browsing” of above) or other possibilities within PHP code itself via PHP commands exec<\/i><\/a> and file_get_contents<\/i><\/a> the latter of which can be very useful during Intranet usage where there is no curl<\/i> available, perhaps. Instead of curl you could use wget<\/a> as another approach.<\/p>\n

      You may want to see a live run (web browsing)<\/a> here at the rjmprogramming.com.au domain or you may want to download the PHP programming source code you could call more_in_tra_ter_net.php<\/a> as you require.<\/p>\n

      \n

      Previous relevant PHP Modes of Use Primer Tutorial<\/a> is shown below.<\/p>\n

      \"PHP<\/a>

      PHP Modes of Use Primer Tutorial<\/p><\/div>\n

      PHP<\/a> is a very flexible programming language. It is probably best known as a server-side language called by a web browser using the http transport layer (ie. web browsing, or “surfing the net”). Let’s list three modes of use of PHP below:<\/p>\n

        \n
      1. Via http transport layer (ie. web browsing, or “surfing the net”) in an Internet<\/a> mode of use (eg: http:\/\/localhost:8888\/in_tra_ter_net.php?SERVER_NAME=localhost) in address bar of a web browser<\/li>\n
      2. Via curl<\/a> in an Internet mode of use (eg. curl http:\/\/localhost:8888\/in_tra_ter_net.php?SERVER_NAME=localhost) at Linux or unix or Windows command line to default output (and you can redirect as required via > outfile<\/i> or >> outfile<\/i> or 2> errfile<\/i> or 2>> errfile<\/i>)<\/li>\n
      3. Via command line PHP in Linux or unix or Windows command line in a command or Intranet<\/a> mode of use (eg. php in_tra_ter_net.php SERVER_NAME=localhost) at a Linux or unix or Windows command line (where the PHP code has been placed, in our example (ie. it is not a URL, but is a file specification of your (Intranet) server)) to default output (or you can redirect as required via > outfile<\/i> or >> outfile<\/i> or 2> errfile<\/i> or 2>> errfile<\/i>)<\/li>\n<\/ol>\n

        Does it matter how the PHP is accessed? Well, yes, it does … sometimes, but not if the code is restricted to a particular mode of usage (but part of what this tutorial is about is to get across how flexible and powerful PHP can be). With the last option above, lots of $_SERVER[]<\/a> variables are undefined, for example.<\/p>\n

          \n
        1. $_SERVER[‘HTTP_COOKIE’] is defined, unlike with curl usage (this seems to be a possibility as a way to detect curl usage). Most $_SERVER[] variables are defined, but $argv[] array is not.<\/li>\n
        2. $_SERVER[‘HTTP_COOKIE’] is undefined, but a lot of the rest of $_SERVER[] variables are as above.<\/li>\n
        3. Lots of $_SERVER[] variables are undefined, with the exception of $_SERVER[‘SCRIPT_FILENAME’] which may help you with Intranet application usage. You cannot enter $_GET[] arguments (on the command line (ie. you will get a syntax error if you try)) so these are undefined, but $argv[] array can be used in that awkward way shown, so that $argv[1] can be arranged to be a lot like $_SERVER[‘QUERY_STRING’] (ie. the bits after ? in a URL).<\/li>\n<\/ol>\n

          So, maybe you have the one mode of use in mind, but you need to think a bit to support all the modes of use, if they are all to have a role with the PHP you write, because, despite these differences it is good to use $_SERVER[] and $_GET[] and $_POST[] and $_SESSION[] and $argv[] and whatever else in terms of variable information PHP offers in terms of attempting to write generic code.<\/p>\n

          Hope you get something out of today’s discussion<\/a> of our Mac OS X MAMP Apache local Web server environment example (hence the http:\/\/localhost:8888\/<\/i> you see in the URLs above), but please bear in mind that there would be other modes of use once you think of other client HTML element ways of accessing PHP (all a lot like the “web browsing” of above) or other possibilities within PHP code itself via PHP commands exec<\/i><\/a> and file_get_contents<\/i><\/a> the latter of which can be very useful during Intranet usage where there is no curl<\/i> available, perhaps. Instead of curl you could use wget<\/a> as another approach.<\/p>\n

          You may want to see a live run (web browsing)<\/a> here at the rjmprogramming.com.au domain or you may want to download the PHP programming source code you could call in_tra_ter_net.php<\/a> as you require.<\/p>\n

          If this was interesting you may be interested in this<\/a> too.<\/p>\n