{"id":50823,"date":"2020-11-08T03:01:25","date_gmt":"2020-11-07T17:01:25","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=50823"},"modified":"2020-11-07T21:51:08","modified_gmt":"2020-11-07T11:51:08","slug":"php-passthru-output-buffering-verb-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/php-passthru-output-buffering-verb-tutorial\/","title":{"rendered":"PHP Passthru Output Buffering Verb Tutorial"},"content":{"rendered":"
\"PHP<\/a>

PHP Passthru Output Buffering Verb Tutorial<\/p><\/div>\n

Yesterday’s PHP Passthru Output Buffering Security Tutorial<\/a> set up a framework for our tightened “defence” of our “Passthru” (PHP) web application woooooooorrrrrrrrlllllld view, but there is scope, still, to improve the “offence”, a move which affects “defence” as well (wouldn’t you know it?!)<\/font>.<\/p>\n

That improvement is to …<\/p>\n

\ngenericize the verb\n<\/p><\/blockquote>\n

… which we find ourselves commonly doing (in our) programming, because of our penchant for functional (ie. action “verb”) rather than “object oriented” (ie. subject or object “noun”) way of writing the code. In other words we tend to think of the whole problem in terms of action points to provide a solution, rather than thinking of the players and working out the roles and behaviours of those players. It’s no big deal which approach you take, as long as you end up with the correct result, in a reasonably timely manner.<\/p>\n

For us, we often model a first draft of such a functional program (or web application) on the “verb” of primary interest, resulting in our first draft containing several hardcodings of the word (or “verb”) “whatis”. And so, “genericization”, for us, is often to turn that\/those “hardcoding(s)” into a variable that can be shared across that code base, hence the “early on” PHP codeline …<\/p>\n

<?php
\n
\n $verb=\"whatis\";
\n<\/code>
\n?><\/p>\n

… as a default first assumption (for the genericization), and a friendly approach for backward compatibility (another personal desire with our code)<\/font>. What is such a “genericization drive”‘s favourite accomplice? For us, it is an HTML select (dropdown) element, as a …<\/p>\n