Socket client creates callback connections

[Jiri Svoboda]

Socket client code (uspace/lib/c/generic/net/socket_client.c) creates callback connections to receive packets from the socket providers.

Instead of simply implementing recv()/recvfrom() using blocking IPC calls, the code receives data from sockets via incoming calls from the socket provider (and queuing them).

This is inappropriate and can lead to problems. An application is not a server and need not process incoming calls. Also, if the application does not process the incoming calls, the socket provider could get blocked.

[Jiri Svoboda]

Socket client code is implemented in an unusual way. I believe it should be rewritten to simply map BSD socket operations to IPC calls.

[Jiri Svoboda]

Since direct IPC calls cannot time out or be aborted (at least not at present), callback might be actually needed.

[Jiri Svoboda]

I stand corrected. It has been established that there is nothing wrong with callback connections to applications.