The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex
At the top of your PHP script:
ReplyDelete<?php
set_time_limit(0);
sleep(30);
// Do stuff here
sleep(30) //wait 30 seconds
ReplyDeleteJust make sure you have your max_execution_time set to a high enough value in your php.ini, otherwise the script will exit before it's complete
You can use sleep() to achieve what you are asking.
ReplyDeleteBe aware that using hard coded delays like you are suggesting will most likely lead to poor design.
If you are waiting for something to happen on the client side I suggest using ajax to issue a notification.
In your java app
ReplyDeletetry {
Thread.sleep(30000L); // 30s
// POST REQUEST
}
catch (Exception e) {}