{"push_id":1490455236,"size":1,"distinct_size":1,"ref":"refs/heads/ONME_2927","head":"3b96ae4c975d06bb258d9dad9a6798688d93b693","before":"facb8823b6ecbcdd4235778606c88ad78fb64ac9","commits":[{"sha":"3b96ae4c975d06bb258d9dad9a6798688d93b693","author":{"name":"Hasnain Virk","email":"e2e6e9d89da8f060022c0918e9231408df554df3@arm.com"},"message":"[ONME-2927] Socket adaptation layer for nanostack\n\nAs a result of major overhaul in Nanostack generally for socket API and especially\nfor TCP, the adaptation layer for mbed-OS is being upgraded.\n\nPreviously, as nanostack was not able to provide receive queue, adaptation layer had been\nfaking it. Now with Stream Socket by default Nanostack provides 2K receive queue and 2K send queue.\nReceive queue size can be changed using setsockopt(). Batre metal nanostack would not provide with any\nreceive queues with Datagram Socket, however in this adaptation layer we introduce a 2K receive queue size\nfor the Datagram Socket as well.\n\nLayer state machine handling is polished to ensure robustness.\n\n::socket_connect() will can return 2 new error codes now. NSAPI_ERROR_ALREADY (like posix EALREADY) in case\nif the connection is in progress or NSAPI_ERROR_IS_CONNECTED (like posix EISCONN) if already connected.\nNSAPI_ERROR_WOULDBLOCK is now mapped directly to nanostack NS_WOULDBLOCK.\n\nNanostackLockGaurd class is introduced which enables us to claim and release mutex using RAII style.","distinct":true,"url":"https://api.github.com/repos/hasnainvirk/mbed-os/commits/3b96ae4c975d06bb258d9dad9a6798688d93b693"}]}
{"actor":{"display_login":"hasnainvirk"}}