[150730] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: dns and software, was Re: Reliable Cloud host ?

daemon@ATHENA.MIT.EDU (Owen DeLong)
Thu Mar 1 20:52:30 2012

From: Owen DeLong <owen@delong.com>
In-Reply-To: <CAP-guGUOUcAXg6C45P2Eq=+4b0Y2HG+vhd2g4xdra9AJw1H5Pg@mail.gmail.com>
Date: Thu, 1 Mar 2012 17:47:52 -0800
To: William Herrin <bill@herrin.us>
Cc: Nanog <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


On Mar 1, 2012, at 5:15 PM, William Herrin wrote:

> On Thu, Mar 1, 2012 at 8:02 PM, Owen DeLong <owen@delong.com> wrote:
>> There's no need to
>> break the current functionality of the underlying system calls and
>> libc functions which would be needed by any such library anyway.
>=20
> Owen,
>=20
> Point to one sentence written by anybody in this entire thread in
> which breaking current functionality was proposed.
>=20
When you said that:

connect(char *name, uint16_t port) should work

That can't work without breaking the existing functionality of the =
connect() system call.

>=20
>>> And because most everybody has made more or less the same errors, =
the
>>> DNS TTL fails to cause their applications to work as intended and
>>> loses its utility as a tool to facilitate renumbering.
>>=20
>> Since I don't write applications for a  living, I will admit I =
haven't rigorously
>> tested any of the libraries out there, but, I'm willing to bet that =
someone,
>> somewhere has probably written a good one by now.
>=20
> Yeah, and if you give me a few weeks I can probably find it amidst all
> the others which aren't so hot.
>=20

I doubt it would take weeks, but, in any case, it's probably faster than =
writing and
debugging your own.

Owen



home help back first fref pref prev next nref lref last post