Noel, > Please review the RFC's I mentioned earlier that deal with command > pipelining. I believe, from a cursory review, that your solution would > break them. I'm interested in SUPPORTING those RFCs when feasible. > > I will object to any change (from anyone) that *prevents* an RFC from > being > implemented, even an elective one.
It's fairly simple to beef up the suggested change to make it compatible with the pipelining stuff. As the pipelining RFC discusses, only a few commands (for our purposes RSET, MAIL, and RCPT) can actually be placed in the middle of a pipeline (section 4.1). This RFC doesn't allow the DATA command (or EHLO, NOOP, or QUIT) to be in the middle of a pipeline, basically for the reasons we've already gone over here. So you put the isReady() check on all commands except RSET, MAIL, and RCPT and you can support RFC 2197 while garnering all the benefits of "fail-fast" command processing. --Peter -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
