<?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 on: Know when and when not to write networking code.</title>
	<atom:link href="http://www.effectiveperlprogramming.com/blog/154/feed" rel="self" type="application/rss+xml" />
	<link>http://www.effectiveperlprogramming.com/blog/154</link>
	<description>Effective Perl Programming - write better, more idiomatic Perl</description>
	<lastBuildDate>Wed, 28 Dec 2011 08:06:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: thomas11</title>
		<link>http://www.effectiveperlprogramming.com/blog/154/comment-page-1#comment-15</link>
		<dc:creator>thomas11</dc:creator>
		<pubDate>Fri, 18 Jun 2010 07:40:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.effectiveperlprogramming.com/?p=154#comment-15</guid>
		<description>brian, check out Email::Stuff: http://search.cpan.org/perldoc?Email::Stuff. That makes sending mail as simple as it should be.</description>
		<content:encoded><![CDATA[<p>brian, check out Email::Stuff: <a href="http://search.cpan.org/perldoc?Email::Stuff" rel="nofollow">http://search.cpan.org/perldoc?Email::Stuff</a>. That makes sending mail as simple as it should be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brian d foy</title>
		<link>http://www.effectiveperlprogramming.com/blog/154/comment-page-1#comment-14</link>
		<dc:creator>brian d foy</dc:creator>
		<pubDate>Wed, 16 Jun 2010 04:17:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.effectiveperlprogramming.com/?p=154#comment-14</guid>
		<description>I&#039;ve added an Email::Simple example, but I think Ricardo took the interface in the wrong direction and that it&#039;s actually harder to use and much more confusing. Most people don&#039;t need to extend the basic interface so Email::Send should be much more straightforward. Really, sending email from within Perl should be as easy as sending it from an email program. You give it some addresses, a subject line, and a message. Something behind the scenes figures out where all the pieces go and how to represent them as objects without dragging the programmer into the weeds.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve added an Email::Simple example, but I think Ricardo took the interface in the wrong direction and that it&#8217;s actually harder to use and much more confusing. Most people don&#8217;t need to extend the basic interface so Email::Send should be much more straightforward. Really, sending email from within Perl should be as easy as sending it from an email program. You give it some addresses, a subject line, and a message. Something behind the scenes figures out where all the pieces go and how to represent them as objects without dragging the programmer into the weeds.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dcmertens</title>
		<link>http://www.effectiveperlprogramming.com/blog/154/comment-page-1#comment-13</link>
		<dc:creator>dcmertens</dc:creator>
		<pubDate>Wed, 16 Jun 2010 01:56:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.effectiveperlprogramming.com/?p=154#comment-13</guid>
		<description>FYI, the maintainer for Email::Send has decided to replace it with the similarly named module Email::Sender. To quote from the Email::Send documentation, &quot;It has API design problems that make it hard to usefully extend and rather than try to deprecate features and slowly ease in a new interface, we&#039;ve released Email::Sender which fixes these problems and others.&quot;</description>
		<content:encoded><![CDATA[<p>FYI, the maintainer for Email::Send has decided to replace it with the similarly named module Email::Sender. To quote from the Email::Send documentation, &#8220;It has API design problems that make it hard to usefully extend and rather than try to deprecate features and slowly ease in a new interface, we&#8217;ve released Email::Sender which fixes these problems and others.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

