<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for phegaro</title><link>http://disqus.com/by/phegaro/</link><description></description><atom:link href="http://disqus.com/phegaro/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 13 Jan 2010 13:04:32 -0000</lastBuildDate><item><title>Re: Receiving Email with Rails</title><link>http://jasonseifer.com/2009/04/24/receving-email-with-rails#comment-29655045</link><description>&lt;p&gt;After looking at this we went with a model where we had a daemon that would just sit there and poll frequently to an IMAP server. We are using a google apps account to do this and it makes this much easier. You dont have to run your own mail server, you can just poll as frequent or non frequent as you want and if you really want instant you can turn on IMAP IDLE support and then you can get the mail as they come in. Since there is only one daemon running we no longer have this problem. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phegaro</dc:creator><pubDate>Wed, 13 Jan 2010 13:04:32 -0000</pubDate></item><item><title>Re: Receiving Email with Rails</title><link>http://jasonseifer.com/2009/04/24/receving-email-with-rails#comment-17390335</link><description>&lt;p&gt;I thought the mail_receiver.rb file will be lauched for each email received and then will stick the email in the queue. I realize that it does not do much but it is creating a ruby process and letting it exit for each email. Is that a high overhead on a system?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phegaro</dc:creator><pubDate>Fri, 25 Sep 2009 14:37:24 -0000</pubDate></item><item><title>Re: Receiving Email with Rails</title><link>http://jasonseifer.com/2009/04/24/receving-email-with-rails#comment-17360937</link><description>&lt;p&gt;Some of the other information that i have read talks about how doing it this way means that a new ruby process is started and killed for each email that comes into the system. According to the math above that would mean that you have about 833 processes being created/deleted per minute on the server. Are you guys having issues with that model?&lt;/p&gt;&lt;p&gt;It seems the polling model avoids this but not sure if the tradeoff for less processes is worth the loss in responsiveness and can we just poll more often to get rid of the issue? Like once ever minute?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phegaro</dc:creator><pubDate>Fri, 25 Sep 2009 03:40:10 -0000</pubDate></item></channel></rss>