Subject: Re: [PATCH] ares_parse_txt_reply: add `record_start` field

Re: [PATCH] ares_parse_txt_reply: add `record_start` field

From: Fedor Indutny <fedor_at_indutny.com>
Date: Wed, 10 Dec 2014 23:49:22 +0700

Jakub,

In the more recent patch, I'm returning the new structure as you have just
said.

The only thing that is missing is an extra field.

Cheers,
Fedor.

On Wed, Dec 10, 2014 at 11:21 PM, Jakub Hrozek <jhrozek_at_redhat.com> wrote:

> On Wed, Dec 10, 2014 at 03:12:16PM +0700, Fedor Indutny wrote:
> > Daniel,
> >
> > I had a strange de-ja-vu about it, and I was right. I already did one
> patch
> > like that in past.
> >
> > Anyway, I redid it - so including both old and new versions for your
> > reviewal.
> >
> > Thank you,
> > Fedor.
>
> As a strange coincidence, I'm just writing a patch for SSSD that adds
> the possibility to also read the TTL for SRV records. I think this is a
> similar case.
>
> So could we, instead of adding a feature-specific name, add a new
> function with a less specific name (ares_parse_txt_ext() perhaps) that
> would return new structure, but the structure would also have some more
> data reserved for future use?
>
Received on 2014-12-10