--jq0ap7NbKX2Kqbes
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Oct 06, 2007 at 10:25:03PM +0200, Jachym Holecek wrote:
> Hello,
>=20
> The binary encoding, which is rather size-efficient and supposedly very
> fast as well (but I don't have numbers yet), is basically Apple bplist
> format. But because Apple doesn't distinguish signed integers vs. unsigne=
d,
> the format differs slightly and uses different version number to avoid
> confusion.
>=20
> On the API side, binary encoding is created/parsed by the following
> functions:
>=20
>   bool prop_dictionary_binary_externalize(prop_dictionary_t, uint8_t **,
>       size_t *);
>   bool prop_dictionary_binary_externalize_to_file(prop_dictionary_t,
>       const char *);
>   prop_dictionary_t prop_dictionary_binary_internalize(uint8_t *, size_t);
>=20
>=20
> and symetrically for prop_array* -- see the diff above for more
> documentation.
>=20
> Comments? I'd like to commit this ASAP as it's a vital prerequisity for
> merging my SoC project.

Will you be changing prop_dictionary_internalize() to accept either=20
format? I think the current prop_dictionary_internalize() should become=20
prop_dictionary_xml_internalize() and prop_dictionary_internalize() will=20
differentiate.

Take care,

Bill

--jq0ap7NbKX2Kqbes
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (NetBSD)

iD8DBQFHC8glWz+3JHUci9cRAuO9AJ0SazPp+kD5EbbWHLJWlt97RL5U+gCdFcv7
XVOUgq9OrMn8a7theIIKtsM=
=y75f
-----END PGP SIGNATURE-----

--jq0ap7NbKX2Kqbes--