Performance experts, Normally to receive e-mails is to pipe their content to script/runner individually from a mail server, sendmail or postfix. Doesn''t this configuration run like Apache 1.3 with CGI, meaning for each e-mail a boot of the entire Rails environment and thus low scalability? Is there anything working like lighttpd-fcgi or going toward its approach? DD -- Posted via http://www.ruby-forum.com/.
We''ve solved this problem by writing a little gateway that receives SMTP and submits each incoming e-mail to Rails as a HTTP post. On 04/04/2006, at 4:22 AM, Doug Dupory wrote:> Performance experts, > > Normally to receive e-mails is to pipe their content to script/runner > individually from a mail server, sendmail or postfix. Doesn''t this > configuration run like Apache 1.3 with CGI, meaning for each e-mail a > boot of the entire Rails environment and thus low scalability? > > Is there anything working like lighttpd-fcgi or going toward its > approach? > > DD > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails
On Apr 3, 2006, at 11:22 AM, Doug Dupory wrote:> Normally to receive e-mails is to pipe their content to script/runner > individually from a mail server, sendmail or postfix. Doesn''t this > configuration run like Apache 1.3 with CGI, meaning for each e-mail a > boot of the entire Rails environment and thus low scalability?You can receive to an account, and retrieve via POP. -- -- Tom Mornini
I have my mail server write the emails to files, and I run a Rails daemon that processes the files. On 4/3/06, Tom Mornini <tmornini@infomania.com> wrote:> > On Apr 3, 2006, at 11:22 AM, Doug Dupory wrote: > > > Normally to receive e-mails is to pipe their content to script/runner > > individually from a mail server, sendmail or postfix. Doesn''t this > > configuration run like Apache 1.3 with CGI, meaning for each e-mail a > > boot of the entire Rails environment and thus low scalability? > > You can receive to an account, and retrieve via POP. > > -- > -- Tom Mornini > > > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060404/e014845d/attachment.html
Pete Yandell wrote:> We''ve solved this problem by writing a little gateway that receives > SMTP and submits each incoming e-mail to Rails as a HTTP post.It sounds great. Is this little gateway open-sourced? If not, the POP or mail file processing can be a quick performance workaround. Thank you for the hints! DD -- Posted via http://www.ruby-forum.com/.
On 05/04/2006, at 3:30 AM, Doug Dupory wrote:> Pete Yandell wrote: >> We''ve solved this problem by writing a little gateway that receives >> SMTP and submits each incoming e-mail to Rails as a HTTP post. > > It sounds great. Is this little gateway open-sourced?Sorry, no. It shouldn''t be hard to write your own though. If you have your own mail server forwarding email in, then you only need to support enough of a subset of SMTP to keep your mail server happy. Cheers, Pete Yandell