James Carlson wrote:
The symmetry argument is this: recvfrom() gives you the inbound packet
source, and sendto() sets the outbound packet destination. This new
feature gives you the inbound packet destination, and it thus must set
the outbound packet *source*. The intentional model is that most
applications can just take the bits from the receive side and copy
them over to the send side without having to look at them. As far as
the application is concerned, the bits are just a token representing
the peer.
Just wondering, does it make sense to have a "send" function
which takes both source and destination addresses as arguments
instead of using ancillary data? To be symmetric, does it
make sense to have a "receive" function to return both source
and destination addresses? I guess an app can have two wrapper
functions which make use of ancillary data to do that. But
if we think that they are useful, we may as well provide them.
--
K. Poon.
[EMAIL PROTECTED]
_______________________________________________
networking-discuss mailing list
[email protected]
