On Mon, 2003-03-24 at 12:42, Erik Nordmark wrote:
> Thus not specifying either of "X" and "not X" leaves the "X" property of
> the address selection at the system default.
And if the application specifies both "X" and "not X"?
In a classic adventure game by Douglas Adams the ability to do this
would have constituted proof of superior intelligence, however here it
is clearly an illegal combination. Having a lot of illegal parameter
combinations in an API is not very desirable, as it requires extra
sanity checks in the implementation.
> An alternate API would be to have one flag per property and always require a
> get before a set.
I think I would prefer this approach. This is clean, no special cases,
and allows simple checking of system defaults. The application can
always store the default bit vector if it creates multiple sockets.
MikaL
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
