> Yes. I'm working on preforking (in fact, I've started to analyze > prefork.c from Apache web server some days ago...). Threads are an > option, but we choose forking for better isolation. Some people say > forking and threading is basically the same in term of perfs, that's > even written in some books dedicated to linux programming, some others > have another opinion.
Good. I'd agree that the difference in performance between a preforking and a multithreaded approach will not be that big. A multithreaded model requires less memory. But with the (hopefully) small footprint of greylisting code this should be neglectable. >> >> So, where is your code? Did I miss a link? >> > Well, I've decided to not put links any more on a mailing list > dedicated to postfix (this is in link with what you wrote in your > first sentence...), and my posts here are very rare. If people want to > take a look at this very young project module, they can find it by > themselves on sourceforge (or by checking my very first posts to this > postfix mailing list) I should have added that all I said was only IMO, of course. It is not up to me to decide what does belong here and what does not. I am happy about anyone offering time and efforts to develop free software or to share something valuable with the community.
