-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>
> Ick and double ick. The data type and interpretation of field
> values is already 100% completely specified by NAME. If you don't
> already know the type of a field by its name, you shouldn't be
> reading it. This just generates another source of errors: now I
> have to write code that not only grabs a field by name, but now I
> have to check whether the type matches what I expect.
>
> If you think you need data types so that a code layer interposed
> between the code that reads the message and the code that uses
> the fields can do conversions, that's just a layer of code that
> doesn't need to be there.
Lee, what you're forcing by saying "All data are strings" is that there is
no room to write any other protocol than the text one.. You can't have
optimized representations of integers, different string encoding formats,
You can't have newlines in strings, etc.
Data aren't strings. Data is data. You can't mandate that all the data
are strings. You can mandate that they are all transfered as strings, but
thats wasteful and restrictive.
Scott
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE5Gu7CpXyM95IyRhURAjsTAJ0eSWp1xHFJw4pz8kOdMBCaX7u9IwCgg1Qk
eH+bsrUjQr0Tzipyp4iNjEU=
=tk5q
-----END PGP SIGNATURE-----
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
