> > There are some things to keep in mind though. Anything that needs > > things that are different in the child will need to be handled > > properly. If the TcpServer object stores PID, that's not good. > > It doesn't; only the parent tracks the PID (in forkserver). It seems > to be sufficient to just do the following:
Yes. > i.e. eliminate the TcpServer object creation inside the child and > change $plugin_loader to be the $qpsmtpd object. I'm trying to remember if there's a reason we had it the other way in the first place. If so, is that reason still valid? > > I don't like either names. 'process' seems to streamy.. and > > spawn.. well.. that's got a negative connotation. > > I didn't like the names either. We could call them John and Robert instead. > > I think the right > > direction probably had to do with talking about the smtp connection. > > pre-connection and post-connection. > > If I hear no objections, I'm going to go with pre-/post-connection > then, since that seems to be the most accurate with the least amount > of implementation leakage. Hrm. So we're talking pre-connection connect disconnect post-connection That's not so bad. -R
