<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments for Michael Caplan</title>
	<atom:link href="http://www.eggplant.ws/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.eggplant.ws/blog</link>
	<description>Ramblings of a web developer</description>
	<pubDate>Mon, 06 Feb 2012 23:54:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Don&#8217;t Forget to Flush by Michael Caplan</title>
		<link>http://www.eggplant.ws/blog/php/dont-forget-to-flush/comment-page-1/#comment-251</link>
		<dc:creator>Michael Caplan</dc:creator>
		<pubDate>Wed, 12 Oct 2011 13:49:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=62#comment-251</guid>
		<description>On load event handlers will only be processed after the complete page has been loaded.  jQuery's .ready() (http://api.jquery.com/ready/) method is probably a better choice if you are just interacting with DOM nodes.</description>
		<content:encoded><![CDATA[<p>On load event handlers will only be processed after the complete page has been loaded.  jQuery&#8217;s .ready() (http://api.jquery.com/ready/) method is probably a better choice if you are just interacting with DOM nodes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Don&#8217;t Forget to Flush by OnLine</title>
		<link>http://www.eggplant.ws/blog/php/dont-forget-to-flush/comment-page-1/#comment-250</link>
		<dc:creator>OnLine</dc:creator>
		<pubDate>Wed, 12 Oct 2011 10:31:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=62#comment-250</guid>
		<description>Hi
For example, if in the HEAD section i have a javascript with an window.onload instruction that selects some html elements from body, then i call flush() before the BODY.
This will send the HEAD code to browser, but if the BODY isn't added in that moment, doesn't it affect the JavaScropt code. 
Or, the window.onload will know and wait till the whole html page is loaded?</description>
		<content:encoded><![CDATA[<p>Hi<br />
For example, if in the HEAD section i have a javascript with an window.onload instruction that selects some html elements from body, then i call flush() before the BODY.<br />
This will send the HEAD code to browser, but if the BODY isn&#8217;t added in that moment, doesn&#8217;t it affect the JavaScropt code.<br />
Or, the window.onload will know and wait till the whole html page is loaded?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Mayday, Mayday, Mayday - PHP Going Down by beakt</title>
		<link>http://www.eggplant.ws/blog/php/mayday-php-going-down/comment-page-1/#comment-237</link>
		<dc:creator>beakt</dc:creator>
		<pubDate>Sat, 28 Aug 2010 08:14:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=28#comment-237</guid>
		<description>This is a terrific article. Not the usual regurgitating of the PHP manual that you usually find when you Google for new knowledge about PHP.  This article is unique and clever.  Very useful, Michael.

I implemented this on my system tonight.  Now, when I forget a semi-colon or screw up my brackets, I can have my web server (by checking $_SERVER['remote_addr']) display the error only for me, and display a friendly apology to my users.  I don't have to go to my Putty window and run 'tail phperror.log' any more!

I can add this: As you may have noticed, this method won't catch a parse error if the definition/registration of the shutdown function is in the same file. But, if you put the definition/registration of the shutdown function into an auto_prepend_file, then it will catch a parse error in your main PHP file called via the URI.</description>
		<content:encoded><![CDATA[<p>This is a terrific article. Not the usual regurgitating of the PHP manual that you usually find when you Google for new knowledge about PHP.  This article is unique and clever.  Very useful, Michael.</p>
<p>I implemented this on my system tonight.  Now, when I forget a semi-colon or screw up my brackets, I can have my web server (by checking $_SERVER['remote_addr']) display the error only for me, and display a friendly apology to my users.  I don&#8217;t have to go to my Putty window and run &#8216;tail phperror.log&#8217; any more!</p>
<p>I can add this: As you may have noticed, this method won&#8217;t catch a parse error if the definition/registration of the shutdown function is in the same file. But, if you put the definition/registration of the shutdown function into an auto_prepend_file, then it will catch a parse error in your main PHP file called via the URI.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Leveraging Omnis within a Heterogeneous Environment through Remote Studio by Paul Mulroney</title>
		<link>http://www.eggplant.ws/blog/php/leveraging-omnis-within-a-heterogeneous-environment-through-remote-studio/comment-page-1/#comment-235</link>
		<dc:creator>Paul Mulroney</dc:creator>
		<pubDate>Thu, 22 Jul 2010 03:33:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=52#comment-235</guid>
		<description>Well written article.  Well done rewriting rStudio!</description>
		<content:encoded><![CDATA[<p>Well written article.  Well done rewriting rStudio!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Mayday, Mayday, Mayday - PHP Going Down by andi zaugg</title>
		<link>http://www.eggplant.ws/blog/php/mayday-php-going-down/comment-page-1/#comment-233</link>
		<dc:creator>andi zaugg</dc:creator>
		<pubDate>Tue, 11 May 2010 12:44:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=28#comment-233</guid>
		<description>cool!
thank you very much!</description>
		<content:encoded><![CDATA[<p>cool!<br />
thank you very much!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Mayday, Mayday, Mayday - PHP Going Down by Christian S.</title>
		<link>http://www.eggplant.ws/blog/php/mayday-php-going-down/comment-page-1/#comment-225</link>
		<dc:creator>Christian S.</dc:creator>
		<pubDate>Tue, 15 Dec 2009 11:34:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=28#comment-225</guid>
		<description>Hey, I am happy about this blog entry. I searched for a solution to catch fatal errors and with Your help I could solve my problem :-)
Thank You very much!</description>
		<content:encoded><![CDATA[<p>Hey, I am happy about this blog entry. I searched for a solution to catch fatal errors and with Your help I could solve my problem <img src='http://www.eggplant.ws/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /><br />
Thank You very much!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Mayday, Mayday, Mayday - PHP Going Down by Claude</title>
		<link>http://www.eggplant.ws/blog/php/mayday-php-going-down/comment-page-1/#comment-221</link>
		<dc:creator>Claude</dc:creator>
		<pubDate>Thu, 22 Oct 2009 18:55:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=28#comment-221</guid>
		<description>Please change the title of your article to something more search engine friendly. Something like this would be much better:

PhP Fatal Error Handling</description>
		<content:encoded><![CDATA[<p>Please change the title of your article to something more search engine friendly. Something like this would be much better:</p>
<p>PhP Fatal Error Handling</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Mayday, Mayday, Mayday - PHP Going Down by rob</title>
		<link>http://www.eggplant.ws/blog/php/mayday-php-going-down/comment-page-1/#comment-215</link>
		<dc:creator>rob</dc:creator>
		<pubDate>Sun, 10 May 2009 15:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=28#comment-215</guid>
		<description>I would not have thought that register_shutdown_function could catch E_PARSE, when even set_error_handler cannot. This is great, thanks!</description>
		<content:encoded><![CDATA[<p>I would not have thought that register_shutdown_function could catch E_PARSE, when even set_error_handler cannot. This is great, thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Don&#8217;t Forget to Flush by Michael Caplan&#8217;s Blog: Don&#8217;t Forget to Flush : Dragonfly Networks</title>
		<link>http://www.eggplant.ws/blog/php/dont-forget-to-flush/comment-page-1/#comment-189</link>
		<dc:creator>Michael Caplan&#8217;s Blog: Don&#8217;t Forget to Flush : Dragonfly Networks</dc:creator>
		<pubDate>Fri, 09 Jan 2009 10:58:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=62#comment-189</guid>
		<description>[...] this recent post to his blog Michael Caplan looks at a feature of PHP that&#8217;s sometimes forgotten when pushing [...]</description>
		<content:encoded><![CDATA[<p>[...] this recent post to his blog Michael Caplan looks at a feature of PHP that&#8217;s sometimes forgotten when pushing [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Don&#8217;t Forget to Flush by Mikael</title>
		<link>http://www.eggplant.ws/blog/php/dont-forget-to-flush/comment-page-1/#comment-188</link>
		<dc:creator>Mikael</dc:creator>
		<pubDate>Wed, 07 Jan 2009 11:54:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=62#comment-188</guid>
		<description>Whoops, missed the last paragraph... sorry !</description>
		<content:encoded><![CDATA[<p>Whoops, missed the last paragraph&#8230; sorry !</p>
]]></content:encoded>
	</item>
</channel>
</rss>

