On Mar 12, 2011, at 12:48 PM, Guy Hulbert wrote: >> So to do that I have basically ported Qpsmtpd to Node.js (and given it a >> decent name while doing so!). >> >> It's still early days - there are no plugins to speak of yet (i.e. no >> queue plugins at all yet), but you might be interested in just looking >> anyway: >> >> https://github.com/baudehlo/Haraka > > Had a look. I recognize bits. Do you have any feeling for how easy it > is to code versus perl and how the performance might be versus qpsmtpd.
Performance is the question I would most like to know the answer to. For qpsmtpd, I'm not sure it matters. Is qpsmtpd often the bottleneck? I should think that the external plugins (clamav, spamassassin, etc) would be the most significant bottlenecks? That being said, if the node.js implementation of qpsmtpd was significantly faster, while consuming significantly fewer resources, it might be an impetus to rewrite SpamAssassin in node.js. I'm currently working on a rather large web project. I'm 99% complete with the backend, and the HTML & CSS is mostly written. Now I get to spend many more days on the javascript client. When I'm completed, I'll have 4 languages employed in the project: (perl, html, css, and javascript). Reducing that to three is quite attractive. Matt
