Harmeet Bedi wrote: > ----- Original Message ----- > From: "Serge Knystautas" <[EMAIL PROTECTED]> > In the past there was talk about creating templates and running those > templates as a record and replay mechanism. I was wondering what everyone > thought of that.
If the template idea is what I think it is, I prefer that approach to using client libraries (like javamail or other such) because they will have rather well behaved, strict behaviors. I'd really like to make sure we can handle numerous kinds of real-world traffic since RFC vs. real world is very different for SMTP. Also would be great to then have good documentation about what and how the standards are supported, so other mail vendors can now how to work with James. I'm sure with some analysis of real server logs we could build standard smtp, pop3, imap, nntp, etc... traffic scripts. Also I'd like to eventually get to component-level testing... from the very basics like a list of 20 or 100 or however many email addresses to make sure our address parsing is handling them correctly. Also higher levels like the file and dbfile and db mail & spool repositories, so we can really throttle the heck out of those independent of the rest of the James code and make sure they're reliable. Anyway, great to see progress on the testing front. -- Serge Knystautas Loki Technologies http://www.lokitech.com/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
