----- Original Message ----- From: "Harmeet Bedi" <[EMAIL PROTECTED]> > I'll say Iterator as it can allow for MX Records > to be read on demand.
Elaborating a bit more on why this may be a good idea - Usu. only one MX record is needed. Not sure why 2 would ever be needed if mail can be sent to the first one. - Most Domains have multiple Nameservers. No need to figure out all the MX records from all the nameservers even for the first. It is not unusual for one of the nameservers to be down. - Most domains have either 1 MX record or have MX records with same priority. So in most cases I think sorting/order doesn't achieve much. - It usu. doesn't matter if you send to an MX address that has lower priority as long as you can send email. - James really does not need to reread the list of mx records so reset for MX Record iteration may be useful but not needed atm. Having said all this, I also have to say that this is not a matter that I care too much about. All suggestions for the return type work for me. Harmeet -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
