Darren Reed wrote:
James Carlson wrote:
Darren Reed writes:
I never even knew about 3XNET...why would I want it?
Ancillary data doesn't work in 3SOCKET. It does in 3XNET. That's the
big reason.
Ok, so there are no compelling reasons to use 3XNET unless someone
needs to interact with ancillary data (whatever that is - there
are no man page references to this on sendmsg/recvmsg.) So my
conclusion is that ancillary data is "rare" and the need for 3XNET
rarer still - but all the same, we provide for it - and thus there
is no reason not to tell people to use libsocket unless they come
back and say "where is my ancillary data?"
This is a failing of ours in many areas. We fail completely to give
our customers any direction. We have bunches of functions, the
discussion of which always leads to something like "no new applications
should use this", but there is nothing like this on the man page.
Is 3XNET socket better than 3SOCKET socket or not? If I am writing
a new application, which should I use? Shouldn't both of the man
pages point to each other with a note about when you should use
one or the other?
--
blu
Quidquid latine dictum sit, altum sonatur.
----------------------------------------------------------------------
Brian Utterback - OP/N1 RPE, Sun Microsystems, Inc.
Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom
_______________________________________________
networking-discuss mailing list
[email protected]
