<?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 SeeIT Consult</title>
	<atom:link href="http://blog.seeit.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.seeit.org</link>
	<description>Web Programming &#038; IT Consultancy</description>
	<lastBuildDate>Mon, 06 Sep 2010 08:40:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on PHP mail() with Ubuntu Desktop and Gmail by Vivek</title>
		<link>http://blog.seeit.org/2010/08/php-mail-with-ubuntu-desktop-and-gmail/comment-page-1/#comment-1264</link>
		<dc:creator>Vivek</dc:creator>
		<pubDate>Mon, 06 Sep 2010 08:40:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.seeit.org/?p=35#comment-1264</guid>
		<description>Thanks Francis.</description>
		<content:encoded><![CDATA[<p>Thanks Francis.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PHP mail() with Ubuntu Desktop and Gmail by Francis</title>
		<link>http://blog.seeit.org/2010/08/php-mail-with-ubuntu-desktop-and-gmail/comment-page-1/#comment-1246</link>
		<dc:creator>Francis</dc:creator>
		<pubDate>Sat, 04 Sep 2010 10:40:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.seeit.org/?p=35#comment-1246</guid>
		<description>Google are the culprits here - they will  not let you use an arbitrary &quot;From&quot; address (for very good reasons).
However as Dennis points out this solution is not for production use.
To solve your problem either:
 - verify the &quot;from&quot; address in your GMail account
or
 - use an alternative SMTP server.</description>
		<content:encoded><![CDATA[<p>Google are the culprits here &#8211; they will  not let you use an arbitrary &#8220;From&#8221; address (for very good reasons).<br />
However as Dennis points out this solution is not for production use.<br />
To solve your problem either:<br />
 &#8211; verify the &#8220;from&#8221; address in your GMail account<br />
or<br />
 &#8211; use an alternative SMTP server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PHP mail() with Ubuntu Desktop and Gmail by Vivek</title>
		<link>http://blog.seeit.org/2010/08/php-mail-with-ubuntu-desktop-and-gmail/comment-page-1/#comment-1239</link>
		<dc:creator>Vivek</dc:creator>
		<pubDate>Fri, 03 Sep 2010 09:46:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.seeit.org/?p=35#comment-1239</guid>
		<description>First i thanks to you for this help. 

Now my mail function is working  fine and sending the mail. But one problem is occur, in From : address my email is sending not that one which is i mentioned in mail(). Even i had done the setting in ssmtp.cnf file. 

Can u please help me to solve this issue.

Thanks once again and waiting ur reply.</description>
		<content:encoded><![CDATA[<p>First i thanks to you for this help. </p>
<p>Now my mail function is working  fine and sending the mail. But one problem is occur, in From : address my email is sending not that one which is i mentioned in mail(). Even i had done the setting in ssmtp.cnf file. </p>
<p>Can u please help me to solve this issue.</p>
<p>Thanks once again and waiting ur reply.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PHP mail() with Ubuntu Desktop and Gmail by Dennis</title>
		<link>http://blog.seeit.org/2010/08/php-mail-with-ubuntu-desktop-and-gmail/comment-page-1/#comment-1205</link>
		<dc:creator>Dennis</dc:creator>
		<pubDate>Sun, 29 Aug 2010 06:44:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.seeit.org/?p=35#comment-1205</guid>
		<description>Hello,

I think people should know that Google has very low limits about the number of emails you can send via your GMail account - on general, you won&#039;t be able to send more than 500 emails a day. So while this is perfect option for low volume mailing, if you have a large number of registered users and want to send a newsletter to them, this won&#039;t work.</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>I think people should know that Google has very low limits about the number of emails you can send via your GMail account &#8211; on general, you won&#8217;t be able to send more than 500 emails a day. So while this is perfect option for low volume mailing, if you have a large number of registered users and want to send a newsletter to them, this won&#8217;t work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PHP mail() with Ubuntu Desktop and Gmail by Francis</title>
		<link>http://blog.seeit.org/2010/08/php-mail-with-ubuntu-desktop-and-gmail/comment-page-1/#comment-1201</link>
		<dc:creator>Francis</dc:creator>
		<pubDate>Sat, 28 Aug 2010 08:59:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.seeit.org/?p=35#comment-1201</guid>
		<description>I agree - if I was developing a mail function in a PHP app I would use something like Swift mailer - it is a very nice piece of kit.

In this case though I was working with someone else&#039;s code and needed the mail() function.

Thanks for the comment.</description>
		<content:encoded><![CDATA[<p>I agree &#8211; if I was developing a mail function in a PHP app I would use something like Swift mailer &#8211; it is a very nice piece of kit.</p>
<p>In this case though I was working with someone else&#8217;s code and needed the mail() function.</p>
<p>Thanks for the comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PHP mail() with Ubuntu Desktop and Gmail by phpuser</title>
		<link>http://blog.seeit.org/2010/08/php-mail-with-ubuntu-desktop-and-gmail/comment-page-1/#comment-1191</link>
		<dc:creator>phpuser</dc:creator>
		<pubDate>Fri, 27 Aug 2010 17:34:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.seeit.org/?p=35#comment-1191</guid>
		<description>I use Swift mailer library to send mail. I think it is a better option for new applications because it is portable.</description>
		<content:encoded><![CDATA[<p>I use Swift mailer library to send mail. I think it is a better option for new applications because it is portable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PHP: The include() include_once() performance debate by Francis</title>
		<link>http://blog.seeit.org/2010/06/php-the-include-include_once-performance-debate/comment-page-1/#comment-1144</link>
		<dc:creator>Francis</dc:creator>
		<pubDate>Wed, 16 Jun 2010 17:52:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.seeit.org/?p=23#comment-1144</guid>
		<description>@Hal / @Greg:

In fairness the intention was to see how quick an include_once()/require_once() is compared to an include()/require() statement when the statement is including the same file more than once - perhaps I should have been more clear about that at the outset. I wouldn&#039;t assume that a single include_once()/require_once() statement is quicker than a single include()/require() statement.

But fair enough - I&#039;ve taken the bait and tweaked the tests - &lt;a href=&quot;#round2&quot; rel=&quot;nofollow&quot;&gt;results are above&lt;/a&gt;. This time each file was only included/required twice and Apache Bench was used to invoke the actual scripts.

@Greg:

Why does this matter? Well, I&#039;d rather know than guess and the debate has been around for years. My conclusions are of course subjective, and (fancy charts notwithstanding) the empirical evidence is that include_once() and require_once() are the quickest - not the slowest.

My conclusions (the use of relative paths and that require_once()/include_once)() are quicker) are my own and I would hardly call them recommendations.

@Everyone:

What about some code to contradict/confirm these findings?</description>
		<content:encoded><![CDATA[<p>@Hal / @Greg:</p>
<p>In fairness the intention was to see how quick an include_once()/require_once() is compared to an include()/require() statement when the statement is including the same file more than once &#8211; perhaps I should have been more clear about that at the outset. I wouldn&#8217;t assume that a single include_once()/require_once() statement is quicker than a single include()/require() statement.</p>
<p>But fair enough &#8211; I&#8217;ve taken the bait and tweaked the tests &#8211; <a href="#round2" rel="nofollow">results are above</a>. This time each file was only included/required twice and Apache Bench was used to invoke the actual scripts.</p>
<p>@Greg:</p>
<p>Why does this matter? Well, I&#8217;d rather know than guess and the debate has been around for years. My conclusions are of course subjective, and (fancy charts notwithstanding) the empirical evidence is that include_once() and require_once() are the quickest &#8211; not the slowest.</p>
<p>My conclusions (the use of relative paths and that require_once()/include_once)() are quicker) are my own and I would hardly call them recommendations.</p>
<p>@Everyone:</p>
<p>What about some code to contradict/confirm these findings?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PHP: The include() include_once() performance debate by Greg Beaver</title>
		<link>http://blog.seeit.org/2010/06/php-the-include-include_once-performance-debate/comment-page-1/#comment-1136</link>
		<dc:creator>Greg Beaver</dc:creator>
		<pubDate>Wed, 16 Jun 2010 04:31:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.seeit.org/?p=23#comment-1136</guid>
		<description>1) If you read the benchmark carefully, you can see that in fact what you want to compare is not the apache server, but the *difference* between the speeds of PHP using the same apache setup.  Note that in each case, a single request is made to the apache server.  In other words, because all of the tests use the same apache setup, and the apache server is polled more than 10,000 times over the course of a minute, the measured difference can be reliably attributed to differences in PHP execution speed, and not in any quirks of apache.
2) include/require are not functions, and if you are executing the same code over and over and over again with a single file, it will hit the realpath cache, and some other optimizations.  You benchmark is not just synthetic, it has absolutely nothing to do with real-world performance of include/require.

Why does this even matter?  You make some assertions with fancy charts, and then proceed to recommend that people actually try what is empirically the slowest options.  Please re-run the benchmarks using proper benchmarking methodology and you will see the drastic errors in your ways.

For a start, perhaps you could steal Paul M. Jones&#039;s script for benchmarking different frameworks:

http://code.google.com/p/web-framework-benchmarks/source/browse/trunk/_siege/siege.php

Related reading:

http://paul-m-jones.com/archives/421</description>
		<content:encoded><![CDATA[<p>1) If you read the benchmark carefully, you can see that in fact what you want to compare is not the apache server, but the *difference* between the speeds of PHP using the same apache setup.  Note that in each case, a single request is made to the apache server.  In other words, because all of the tests use the same apache setup, and the apache server is polled more than 10,000 times over the course of a minute, the measured difference can be reliably attributed to differences in PHP execution speed, and not in any quirks of apache.<br />
2) include/require are not functions, and if you are executing the same code over and over and over again with a single file, it will hit the realpath cache, and some other optimizations.  You benchmark is not just synthetic, it has absolutely nothing to do with real-world performance of include/require.</p>
<p>Why does this even matter?  You make some assertions with fancy charts, and then proceed to recommend that people actually try what is empirically the slowest options.  Please re-run the benchmarks using proper benchmarking methodology and you will see the drastic errors in your ways.</p>
<p>For a start, perhaps you could steal Paul M. Jones&#8217;s script for benchmarking different frameworks:</p>
<p><a href="http://code.google.com/p/web-framework-benchmarks/source/browse/trunk/_siege/siege.php" rel="nofollow">http://code.google.com/p/web-framework-benchmarks/source/browse/trunk/_siege/siege.php</a></p>
<p>Related reading:</p>
<p><a href="http://paul-m-jones.com/archives/421" rel="nofollow">http://paul-m-jones.com/archives/421</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PHP: The include() include_once() performance debate by Francis</title>
		<link>http://blog.seeit.org/2010/06/php-the-include-include_once-performance-debate/comment-page-1/#comment-1122</link>
		<dc:creator>Francis</dc:creator>
		<pubDate>Tue, 15 Jun 2010 08:24:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.seeit.org/?p=23#comment-1122</guid>
		<description>@Hal / @Greg:

I agree - the test set up is totally artificial. However I wanted to look at the PHP functions themselves rather than start benchmarking the Apache server. The tests on http://markmail.org/message/hxzqcgrzrh6szce4 would be interesting to revisit today.

@Jaik:

I wouldn&#039;t be too bothered with the performance differences myself - as Greg points out including the same trivial file 10,000 times hardly demonstrates anything tangible. I prefer to code in such a way that a file only ever needs to be included once anyway (by encapsulating in a class or a function).

@Sjan:

I didn&#039;t look at __autoload() for the simple reason that I avoid using it. I did use it earlier in the Tina framework, but I found that I ended up colliding with another plugin author&#039;s __autoload() function. In an environment where everyone is playing nicely with each other I would like to use __autoload(), but in Wordpress that doesn&#039;t happen!</description>
		<content:encoded><![CDATA[<p>@Hal / @Greg:</p>
<p>I agree &#8211; the test set up is totally artificial. However I wanted to look at the PHP functions themselves rather than start benchmarking the Apache server. The tests on <a href="http://markmail.org/message/hxzqcgrzrh6szce4" rel="nofollow">http://markmail.org/message/hxzqcgrzrh6szce4</a> would be interesting to revisit today.</p>
<p>@Jaik:</p>
<p>I wouldn&#8217;t be too bothered with the performance differences myself &#8211; as Greg points out including the same trivial file 10,000 times hardly demonstrates anything tangible. I prefer to code in such a way that a file only ever needs to be included once anyway (by encapsulating in a class or a function).</p>
<p>@Sjan:</p>
<p>I didn&#8217;t look at __autoload() for the simple reason that I avoid using it. I did use it earlier in the Tina framework, but I found that I ended up colliding with another plugin author&#8217;s __autoload() function. In an environment where everyone is playing nicely with each other I would like to use __autoload(), but in Wordpress that doesn&#8217;t happen!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PHP: The include() include_once() performance debate by Jaik Dean</title>
		<link>http://blog.seeit.org/2010/06/php-the-include-include_once-performance-debate/comment-page-1/#comment-1121</link>
		<dc:creator>Jaik Dean</dc:creator>
		<pubDate>Tue, 15 Jun 2010 08:10:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.seeit.org/?p=23#comment-1121</guid>
		<description>Surely you should just use whichever function is relevant in each situation? If you&#039;re getting any tangible real-world performance benefit from switching between these functions then I feel your script probably has some much more serious issues that need addressing before such micro-optimisations.</description>
		<content:encoded><![CDATA[<p>Surely you should just use whichever function is relevant in each situation? If you&#8217;re getting any tangible real-world performance benefit from switching between these functions then I feel your script probably has some much more serious issues that need addressing before such micro-optimisations.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using apc
Page Caching using apc (user agent is rejected)
Database Caching 1/20 queries in 0.138 seconds using apc

Served from: blog.seeit.org @ 2010-09-09 19:06:59 -->