They do maintain it, yes..
But it is basically working (but for my problem) so I think there's no
strong ownership of that code.
As a result I am trying to move resip (at least, my copy) to c-ares and
add the necessary IPv6 support where needed. I always favour using
active and maintained projects over trying to maintain everything ourselves.
I think the original reason for the fork could have been IPv6, but don't
quote me on that. c-ares has since added support for IPv6 so I think
there's a chance that we could remove resip-ares for c-ares.
On 11-05-13 01:36 PM, Daniel Stenberg wrote:
> On Fri, 13 May 2011, David Stuart wrote:
>
>> As a further follow-up to this. c-ares seems to suffer from the same
>> problem as the resip-ares fork in this regard (though the code is
>> substantially different).
>
> Can I just add that I had no idea resip-ares existed until your mail
> just now.
>
> Do you know what they've made with it and if they still maintain a
> separate ares fork?
>
-- David Stuart, CounterPath Email: dstuart (at) counterpath (dot) com Phone: (613) 254-8886 x2234 Web: http://www.counterpath.com/ Address: 310 - 350 Terry Fox Drive, Kanata Ontario, K2K 2P5Received on 2011-05-13