Subject: Re: DHCP client, integration with ifconfig, etc.
To: None <tech-net@NetBSD.ORG>
From: Christian Kuhtz <firstname.lastname@example.org>
Date: 02/12/1997 12:59:45
Returning a new error value is IMHO one of the worst ways to solve this. It
may seem elegant, however, being able to call a generic handler when this
global condition is reached appears to me like a much cleaner design, aside
from the fact that it is much easier to retrofit current implementations with
On Wed, 12 Feb 1997 18:00:25 +0100, Guenther Grau <email@example.com> wrote:
> This looks reasonable to me, although it would be nicer if
> applications wouldn't even notice that the IP-address has changed,
> but I guess this is not really that easy to handle:-/ What is an
> application excpected to do, when it get's such a message, in
> whatever way? Should it shutdown all the connections it maintains
> and reestablish them if/when a new IP-address is available? Is
> there still time for the application to shutdown, because it will
> get this message when the IP-address has already expired? How do
> other OS' and the applications thereon handle this?
Christian Kuhtz <firstname.lastname@example.org> (personal) <email@example.com> (work)
".com is a mistake."