Why do the st_recvmsg()/st_sendmsg() docs refer to UDP sockets?

I'm curious as to why the docs constain st_sendmsg() and st_recvmsg()
to UDP?

To quote from
http://state-threads.sourceforge.net/docs/reference.html#sendmsg "A
file descriptor object identifier (see st_netfd_t) representing a UDP
socket"

But I don't see anything in the st code that requires this constraint,
furthermore I've long used st_sendmsg() and st_recvmsg() on TCP
sockets as it's the only way to do an inter-process fdpass with this
sort of code:

  control->cmsg_level = SOL_SOCKET;
  control->cmsg_type = SCM_RIGHTS;

My guess is that it's just an historical accident in the docs that
might have been cloned from st_sendto()/st_recvfrom() function - which
are constrained to UDP.


Mark.

------------------------------------------------------------------------------
Learn Windows Azure Live!  Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for 
developers. It will provide a great way to learn Windows Azure and what it 
provides. You can attend the event by watching it streamed LIVE online.  
Learn more at http://p.sf.net/sfu/ms-windowsazure