[En-Nut-Discussion] NutTcpAccept() timeout

[Harald Kipp]

I understand your view in general, but we do not have NutTcpTryReceive()
or NutTcpTrySend() either. Setting

   NutTcpSetSockOpt(sock, SO_RCVTIMEO, &tmo, sizeof(tmo));

affects the standard API call and it is difficult to explain, why
NutTcpReceive() takes care of this option, but NutTcpAccept()
ignores it and the user is forced to call NutTcpTryAccept() instead.

Harald

At 11:06 20.07.2006 -0300, you wrote:
> From the API point of view, I actually prefer the former, because at the
>first sight it's obvious that it has a different behavior. The function name
>expresses what it does, and that's what the API designer should strive for.
>Just my 2cents...