{"id":17312,"date":"2015-09-22T05:01:41","date_gmt":"2015-09-21T19:01:41","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=17312"},"modified":"2015-09-22T10:23:13","modified_gmt":"2015-09-22T00:23:13","slug":"client-pre-emptive-iframe-crontab-curl-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/client-pre-emptive-iframe-crontab-curl-tutorial\/","title":{"rendered":"Client Pre-emptive Iframe Crontab Curl Tutorial"},"content":{"rendered":"
\"Client<\/a>

Client Pre-emptive Iframe Crontab Curl Tutorial<\/p><\/div>\n

Recap to yesterday …<\/p>\n

\n

We don’t know if “Client Pre-emptive Iframe”<\/i> is a concept, but even if it isn’t, we’d like to say something about it today.<\/p>\n

To us, it’s the idea that in the web application world, at the client end of things, with Javascript, though there is no file manipulation as such, there is what we’d like to term “Client Pre-emptive Iframe”<\/i>, as an idea that Javascript functionality teamed with an HTML iframe<\/a> (and its onload<\/i> event logic) can achieve a bit of what a serverside language like PHP or ASP.Net can achieve, in terms of using server files, by guessing about their existence as the src= parameter of an HTML iframe element, and sort of “sucking it, and seeing” whether the operation succeeds … ie. pre-emptive guessing, we guess. The point is, even if the guess is wrong, no huge harm is done, and in Javascript, it can be checked for, so why stress out, man<\/strike> person?<\/p>\n<\/blockquote>\n

… as you can see, also, at Client Pre-emptive Iframe Primer Tutorial<\/a>.<\/p>\n

Today’s HTML\/Javascript work of continuous_report.html<\/a> teams this concept with a Linux<\/a> web server’s …<\/p>\n