That might be cool, I think that we need to carfully look at performance of any config related stuff. The config should be read once, and for things like dbmail-smtp it should do as little as possible as it is read each time. I know the lmtpd is the answer to not re-reading configs each time but not everyone will be able to use it. I would be intersted in what you were thinking about run-time dynamic config?
Thanks, Leif > If that (config in the database) is going to happen again, one thing that > is > worth considering is a run-time dynamic config system, so you can change > the > behavior of dbmail on the fly. If it's worthwhile, I'll take a crack at it > this weekend. > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Aaron Stone > Sent: Wednesday, March 03, 2004 7:06 PM > To: dbmail-dev@dbmail.org > Subject: Re: [Dbmail-dev] adding FreeConfig while tracking down memory > leaks > .. was format errors in calls to trace() > > Oh, I just read the patch again and now I get it :-P > > Maybe a more thorough refactoring of the configuration code is in order? > At > the very least, it looks like we're going to be moving a lot of the > configuration back into the database during the 2.1 development phase. > > Aaron > > _______________________________________________ > Dbmail-dev mailing list > Dbmail-dev@dbmail.org > http://twister.fastxs.net/mailman/listinfo/dbmail-dev >
