Darren Reed writes: > >By that argument, we might as well name the constant NE_XYZZY. Obviously, > >the intent is also to describe the event. My view is that a good event > >description should include both the name of the object and the event > >occurring on it; thus NE_ADDRESS_CHANGE (or NE_ADDR_CHANGE) is good. > > > > > > Ok, so you've thrown up one name, NE_ILL_*, which I don't > beieve is a good choice, do you have any other suggestions > on how to better qualify the UP/DOWN event names?
Some variation on "physical" and "logical" would also work, as those are the names used in ifconfig(1M). -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
