Re: NT 3.51 dhcp client and server ip address

[Ted Lemon <[e-mail]>]

> I have some ideas where a singular server identifier might make developing
> a server redundancy protocol easier, but nothing that I can catagorize
> as strong.  What sort of things am I missing?

Hm.   You can call it strong or not, but my reason for using a single
identifier was that I wanted to be able to do a straight comparison on
server identifiers sent back by clients, rather than having to do a
(hashed) table lookup.   In general, it just seems like a bad idea to
have multiple identifiers referring to the same object.

			       _MelloN_