Not sure, in case of c-ares all the parsing from raw RDATA into
meaningful C structures is done by c-ares itself. But if there are
more projects that implement the parsing themselves, maybe they would
benefit from a shared library. Of couse there's work converting them
from whatever API they use internally to the new one etc..
On Mon, Feb 28, 2011 at 10:32 PM, Adam Stokes <ajs(a)redhat.com> wrote:
Lastly, what are your thoughts on creating a separate library for
these types of routines so anyone can easily benefit?
----- Original Message -----
> Awesome thanks so much Jakub. I'm reading those usage rules now.
> Lastly I see you guys are using the ares library, is this something
> that should be considered with Matahari and have you guys run into any
> blocking issues with the library in particular?
>
> Thanks!
>
> ----- Original Message -----
> > Hi,
> >
> > This looks fine (visually, haven't tested) although the code does
> > not
> > seem to implement "Usage Rules" of RFC 2782 (pages 5,6 of
> >
http://www.ietf.org/rfc/rfc2782.txt)
> >
> > We've been down this route in SSSD couple of months back, so feel
> > free
> > to check out
> >
https://fedorahosted.org/sssd/browser/src/resolv/async_resolv.c
> > The three last functions could be of interest -
> > resolv_sort_srv_reply(), reply_weight_rearrange() and
> > reply_priority_sort().
> >
> > Hope this helps,
> > Jakub
>
> --
> __ __
> .-----.| |_.-----.| |--.-----.-----.
> |__ --|| _| _ || <| -__|__ --|
> |_____||____|_____||__|__|_____|_____|
> .----------------------------------.
> ( ajs(a)redhat.com || 919.754.4187 )
> `----------------------------------'
--
__ __
.-----.| |_.-----.| |--.-----.-----.
|__ --|| _| _ || <| -__|__ --|
|_____||____|_____||__|__|_____|_____|
.----------------------------------.
( ajs(a)redhat.com || 919.754.4187 )
`----------------------------------'