Mark Michelson wrote:
Your opinions pretty much mimic mine.
Yay.
1) Don't write a DNS library. It's been done many times before by others, so just use those. 2) Don't jostle things where it is unnecessary. As far as implementation details, it's far too early to be criticizing those, so I just barely skimmed to make sure they made some amount of sense. I imagine as things get more nitty-gritty, you'll come up with a more detailed plan with structures, API calls, etc. With regards to the two third-party libraries you presented, my initial impression is that I like c-ares better. Honestly, I find the on-site documentation for both libraries to be pretty bad, but c-ares is the better of the two. I also like that c-ares has functions for parsing different DNS record types. I also like that c-ares is hosted on github. Other things that would influence me on this decision:
<snip> Agreed. I'd also add Package Availability to your list. Cheers, -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com & www.asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
