Serge Sozonoff wrote:
Yeah, the DNSServer code uses a Vector as the underlying implementation and a custom comparator. Then all we really need to do is change the method contract to maintain that this is a List and not a Collection.Hi Aaron,The James DNSServer class has a custom Comparator and does the ordering. It returns an ordered list.
As for SortedSet vs. List, it logically makes more sense to have it as a SortedSet since it wouldn't make sense to have multiple MX records to the same IP address. But you never know, I don't think DNS could enforce this... I guess we just do extra checks as we add the IP addresses and avoid duplication. I might just make it a List to avoid working this out... the benefit of making it a SortedSet seem minimal to me.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
