Specific Enumeration used for asynchronous operations.
Data Structures | |
struct | tstrSocketAcceptMsg |
Socket accept status. More... | |
struct | tstrSocketBindMsg |
Socket bind status. More... | |
struct | tstrSocketConnectMsg |
Socket connect status. More... | |
struct | tstrSocketListenMsg |
Socket listen status. More... | |
struct | tstrSocketRecvMsg |
Socket recv status. More... | |
Enumerations | |
enum | tenuSocketCallbackMsgType { SOCKET_MSG_BIND = 1, SOCKET_MSG_LISTEN, SOCKET_MSG_DNS_RESOLVE, SOCKET_MSG_ACCEPT, SOCKET_MSG_CONNECT, SOCKET_MSG_RECV, SOCKET_MSG_SEND, SOCKET_MSG_SENDTO, SOCKET_MSG_RECVFROM, SOCKET_MSG_SECURE } |
Asynchronous APIs make use of callback functions in-order to return back the results once the corresponding socket operation is completed. Hence resuming the normal execution of the application code while the socket operation returns the results. Callback functions expect event messages to be passed in, in-order to identify the operation they're returning the results for. The following enum identifies the type of events that are received in the callback function. More... | |
Asynchronous APIs make use of callback functions in-order to return back the results once the corresponding socket operation is completed. Hence resuming the normal execution of the application code while the socket operation returns the results. Callback functions expect event messages to be passed in, in-order to identify the operation they're returning the results for. The following enum identifies the type of events that are received in the callback function.
Application Use: In order for application developers to handle the pending events from the network controller through the callback functions, a function call must be made to the function @ref m2m_wifi_handle_events at least once for each socket operation.