Comments on: AJAX Logfile Tailer & Viewer http://commavee.com/2007/04/13/ajax-logfile-tailer-viewer/ from John Minnihan, founder of Freepository. Fri, 05 Mar 2010 05:58:53 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: John Minnihan http://commavee.com/2007/04/13/ajax-logfile-tailer-viewer/comment-page-1/#comment-44235 John Minnihan Wed, 03 Feb 2010 18:24:30 +0000 http://commavee.com/2007/04/13/ajax-logfile-tailer-viewer/#comment-44235 Screen flicker on any div update is usually the result of a collision of heights of the elements that are changing.<br><br>Be sure that there's adequate space (or at least no overlap) between the div you are updating and any adjacent divs. The flicker is caused when the DOM renders the new placement & has to 'adjust' the overlap. Screen flicker on any div update is usually the result of a collision of heights of the elements that are changing.

Be sure that there's adequate space (or at least no overlap) between the div you are updating and any adjacent divs. The flicker is caused when the DOM renders the new placement & has to 'adjust' the overlap.

]]> By: John http://commavee.com/2007/04/13/ajax-logfile-tailer-viewer/comment-page-1/#comment-44230 John Wed, 03 Feb 2010 02:27:33 +0000 http://commavee.com/2007/04/13/ajax-logfile-tailer-viewer/#comment-44230 I notice there is a screen/div flicker/back-out when the div updates is there a way to eliminate this?<br>I have try'ed to Google something but could not find anything relative.<br>Thanks for a great script thought. I notice there is a screen/div flicker/back-out when the div updates is there a way to eliminate this?
I have try'ed to Google something but could not find anything relative.
Thanks for a great script thought.

]]> By: John Minnihan http://commavee.com/2007/04/13/ajax-logfile-tailer-viewer/comment-page-1/#comment-44128 John Minnihan Wed, 20 Jan 2010 18:45:00 +0000 http://commavee.com/2007/04/13/ajax-logfile-tailer-viewer/#comment-44128 In theory, that should be possible. Create two of each of the functions or more cleanly, allow them to take arguments that point to the correct log file script & div to update.<br><br>Use my reload.php script, the page that opens in the test harness with the big 'Generate Log Output' button, as the way to test:<br><br><?<br>$log = fopen("./ajax-logtail-viewer.log", "a");<br>$ip = $_SERVER['REMOTE_ADDR'];<br>$page = $_SERVER['SCRIPT_NAME'];<br>fwrite($log, "ALFV - " . $ip . " loaded " . $page . " at " . gmstrftime ("%b %d %Y %H:%M:%S", time()) . "n");<br>?><br><br><html><br><br><button style="font-size:30px;" onclick="window.location.reload()";>Generate Log Output</button><br><br><br/><br/><br><br>Click the button you see above to reload this page. It will generate log output that may be viewed in the Log Viewer.<br></html><br><br>Create two of these one, say reload-1.php and reload-2.php and make -1 point to the first log file & -2 point to the second one. This is just a means to generate output & does not actually implement any part of the logtail viewer, so don't get too hung up on it. Make corresponding adjustments in the logtail viewer itself to test this technique.<br><br>If you get it to work like that, let me know. In theory, that should be possible. Create two of each of the functions or more cleanly, allow them to take arguments that point to the correct log file script & div to update.

Use my reload.php script, the page that opens in the test harness with the big 'Generate Log Output' button, as the way to test:

<?
$log = fopen(“./ajax-logtail-viewer.log”, “a”);
$ip = $_SERVER['REMOTE_ADDR'];
$page = $_SERVER['SCRIPT_NAME'];
fwrite($log, “ALFV – ” . $ip . ” loaded ” . $page . ” at ” . gmstrftime (“%b %d %Y %H:%M:%S”, time()) . “n”);
?>

<html>

<button style=”font-size:30px;” onclick=”window.location.reload()”;>Generate Log Output</button>

Click the button you see above to reload this page. It will generate log output that may be viewed in the Log Viewer.
</html>

Create two of these one, say reload-1.php and reload-2.php and make -1 point to the first log file & -2 point to the second one. This is just a means to generate output & does not actually implement any part of the logtail viewer, so don't get too hung up on it. Make corresponding adjustments in the logtail viewer itself to test this technique.

If you get it to work like that, let me know.

]]> By: Chris http://commavee.com/2007/04/13/ajax-logfile-tailer-viewer/comment-page-1/#comment-44124 Chris Wed, 20 Jan 2010 09:24:44 +0000 http://commavee.com/2007/04/13/ajax-logfile-tailer-viewer/#comment-44124 Is there a way to get two of these going on the same page with different logs? Is there a way to get two of these going on the same page with different logs?

]]> By: John Minnihan http://commavee.com/2007/04/13/ajax-logfile-tailer-viewer/comment-page-1/#comment-43888 John Minnihan Wed, 29 Jul 2009 20:40:19 +0000 http://commavee.com/2007/04/13/ajax-logfile-tailer-viewer/#comment-43888 Hey all -<br><br>To everyone who has visited this page, checked the example and found that it didn't refresh as advertised, please accept my apologies.<br><br>I had made some server-side configuration changes to Apache that resulted in far-too-aggressive caching of page content. This had the affect of not refreshing the logtail <div> in the example.<br><br>There is (and was) nothing wrong with the script itself, so if you had downloaded it & attempted to use it on your own server, it would have worked for you.<br><br>Again, apologies to anyone that was blocked by this server-side configuration error on my part. I've restored the original config & the example now functions as it should. Hey all -

To everyone who has visited this page, checked the example and found that it didn't refresh as advertised, please accept my apologies.

I had made some server-side configuration changes to Apache that resulted in far-too-aggressive caching of page content. This had the affect of not refreshing the logtail <div> in the example.

There is (and was) nothing wrong with the script itself, so if you had downloaded it & attempted to use it on your own server, it would have worked for you.

Again, apologies to anyone that was blocked by this server-side configuration error on my part. I've restored the original config & the example now functions as it should.

]]>