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: Thu, 22 May 2014 17:02:19 +0400

Hello Saul!

As an alternative, I could use `NULL` txt field to indicate a record
separation, but this
will break the existing code.

Unfortunately, there is no certain description of how TXT records should be
used after
parsing. Clearly some people may want to get each chunk of each record
separately
and use them as they want to. Concatenation will definitely make c-ares
unusable for
them.

Cheers,
Fedor.

On Thu, May 22, 2014 at 10:51 AM, Saúl Ibarra Corretgé <saghul_at_gmail.com>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 05/19/2014 09:19 PM, Fedor Indutny wrote:
> > Introduce `record_start` field, indicating start of new TXT record,
> > thus allowing to differentiate chunks in the same record, from a
> > chunks in a different record.
>
> Hey Fedor!
>
> This patch changes the ABI, any chance this could be done by
> concatenating the chunks and thus not requiring that extra field in
> the ares_txt_reply struct?
>
> - --
> Saúl Ibarra Corretgé
> bettercallsaghul.com
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: Using GnuPG with Icedove - http://www.enigmail.net/
>
> iQIcBAEBAgAGBQJTfZ5fAAoJEEEOVVOum8BZkPkQAI/0KXcb+jyv17pgWZvHzoyD
> DesPcht2ZXh3l47aIdWrbQlVlgDqtqFmYT6eiMVoG03M/0C6uySXUGzqVz5LTFf1
> EBiHGluGNbigHAfv8Rj+Cm++fDkuyGdDpwwqWhgytGGKHB/SCA8wlCEFr+eFgxEK
> z2+sy0NKFGOZdZc1sholju8gYalUvTD3buKHgl0vKGcBTCIZOn12IiaySzeILHp/
> FlBFl6v8ihqg8xEynhg4I9F/2AMWSjRXYjxyCB2lcc+9yAgy6QcSu6nimogstlM+
> grlY3aMscVfEXAy4bmAFfKgxcbma6SX7tRDVNjEM2jZQITxL2+/MBEo00ny0YdDx
> IYbUbjEBQSpNHkQtb9QQofgDfYHXCbsNjy5cNpIDHA2ENCySYzRkNAz2I/36p9g9
> RigP8MYqYrgbZqjZsP47PSFlrmdhTGzWqss8dfLjJoQeIdmUnrLaUdU7h7mIGveq
> IP3fbWhMoYJYnsvL3DP0Tvv/ChsitNuOkHIKP+xtOTZK/YMucJylxVNV99RvqvKZ
> UY4SurNd60hN5N89+m92Yrgu8wokCj3Ya3XPmNd2Ufo18NrA1t7NQSPSo/h9frek
> Sjaquzv2GmpnvLKO8dCJw0PwpIve1+T4weWk9kjstXbr8R55g5+4V3lbfI7yJcSH
> pPOL/8QrEUfZCiOnPwTy
> =GebV
> -----END PGP SIGNATURE-----
>
Received on 2014-05-22