[reSIProcate] Followup on c-ares support

[Alan Hawrylyshen]

On Nov 22, 2008, at 15:20 , Brad Spencer wrote:

> First, thanks again for the help so far.  With a little more digging
> and some help from others, including the c-ares mailing list, I've
> managed to get further along in using c-ares with resiprocate.
>
> I have identified a set of "obvious" features that resiprocate depends
> on simply by looking at the API differences between contrib/ares and
> c-ares.  I have not searched for embedded behavioural changes that may
> have been made to contrib/ares without API changes.  However,
> especially if c-ares vs contrib/ares were to remain a choice at
> configuration time, I think this is okay, at least as a starting point
> because c-ares "works".
>
> The attached patch will allow resiprocate to be configured against the
> trunk version of c-ares (1.5.3 + patches).  Of course, it still allows
> resiprocate to be configured to use contrib/ares as well.

Brad;

Thanks for looking into this. There is certainly some benefit to re- 
joining the world-at-large with our resolver library. Your efforts are  
appreciated. Please keep us up-to-date.
Very few functional changes were made IIRC; the big changes were  
extending ARES to support AAAA NAPTR and SRV records, which our  
original version did not.

Thanks
Alan Hawrylyshen
--
Alan Hawrylyshen
a l a n a t p o l y p h a s e d o t c a