sioc縮寫(xiě)是什么意思

SIOC英文含義

1、SIOC的英文全稱(chēng)：Semantically Interlinked Online Community | 中文意思：───語(yǔ)義關(guān)聯(lián)的在線(xiàn)社區

2、SIOC的英文全稱(chēng)：Serial Input/Output Controller | 中文意思：───串行輸入/輸出控制器

3、SIOC的英文全稱(chēng)：Strategic Intelligence Officers Course | 中文意思：───戰略情報官員課程

4、SIOC的英文全稱(chēng)：Semantically Interlinked Online Communities | 中文意思：───語(yǔ)義關(guān)聯(lián)的在線(xiàn)社區

5、SIOC的英文全稱(chēng)：Strategic Information and Operations Center | 中文意思：───戰略情報和行動(dòng)中心

6、SIOC的英文全稱(chēng)：Subaru Impreza Owners Club | 中文意思：───斯巴魯車(chē)主俱樂(lè )部

7、SIOC的英文全稱(chēng)：Shanghai Institute of Organic Chemistry (China) | 中文意思：───上海有機化學(xué)研究所(中國)

8、SIOC的英文全稱(chēng)：Serial Input Output Controller | 中文意思：───串行輸入輸出控制器

9、SIOC的英文全稱(chēng)：Ship in Original Carton (packaging) | 中文意思：───船在原紙箱(包裝)

int recv( SOCKET s, char FAR *buf, int len, int flags ); 中的flags 取 0是什么意思

你的困惑時(shí) 網(wǎng)上都是說(shuō)flag是什么什么意思

而我們一般用的時(shí)候都是置零

可能樓主想多了

flag有幾個(gè)特殊參數 比如MSG_OOB MSG_BONTROUTE

這些都表示recv在接受數據時(shí)要遵循特殊規則，

所以當flag=0時(shí) 就默認是普通接受數據 模式

也就是：從接口s 緩存區buf讀取len字節的數據 這就這樣 沒(méi)有什么特殊意思

int recv( SOCKET s, char FAR *buf, int len, int flags ); 中的flags 取 0是什么意思

查看MSDN：

recv Function

The recv function receives data from a connected or bound socket.

int recv(

__in SOCKET s,

__out char* buf,

__in int len,

__in int flags

);

Parameters

s

The descriptor that identifies a connected socket.

buf

The buffer for incoming data.

len

The length, in bytes, of the buf parameter.

flags

A pointer to flags that influences the behavior of this function. See remarks below.

其中：

Remarks

The recv function is used to read incoming data on connection-oriented sockets, or connectionless sockets. When using a connection-oriented protocol, the sockets must be connected before calling recv. When using a connectionless protocol, the sockets must be bound before calling recv.

The local address of the socket must be known. For server applications, use an explicit bind function or an implicit accept or WSAAccept function. Explicit binding is discouraged for client applications. For client applications, the socket can become bound implicitly to a local address using connect, WSAConnect, sendto, WSASendTo, or WSAJoinLeaf.

For connected or connectionless sockets, the recv function restricts the addresses from which received messages are accepted. The function only returns messages from the remote address specified in the connection. Messages from other addresses are (silently) discarded.

For connection-oriented sockets (type SOCK_STREAM for example), calling recv will return as much data as is currently available—up to the size of the buffer specified. If the socket has been configured for in-line reception of OOB data (socket option SO_OOBINLINE) and OOB data is yet unread, only OOB data will be returned. The application can use the ioctlsocket or WSAIoctlSIOCATMARK command to determine whether any more OOB data remains to be read.

For connectionless sockets (type SOCK_DGRAM or other message-oriented sockets), data is extracted from the first enqueued datagram (message) from the destination address specified by the connect function.

If the datagram or message is larger than the buffer specified, the buffer is filled with the first part of the datagram, and recv generates the error WSAEMSGSIZE. For unreliable protocols (for example, UDP) the excess data is lost; for reliable protocols, the data is retained by the service provider until it is successfully read by calling recv with a large enough buffer.

If no incoming data is available at the socket, the recv call blocks and waits for data to arrive according to the blocking rules defined for WSARecv with the MSG_PARTIAL flag not set unless the socket is nonblocking. In this case, a value of SOCKET_ERROR is returned with the error code set to WSAEWOULDBLOCK. The select, WSAAsyncSelect, or WSAEventSelect functions can be used to determine when more data arrives.

If the socket is connection oriented and the remote side has shut down the connection gracefully, and all data has been received, a recv will complete immediately with zero bytes received. If the connection has been reset, a recv will fail with the error WSAECONNRESET.

Note When issuing a blocking Winsock call, such as send, recv, select, accept, or connect function calls, Winsock may need to wait for a network event before the call can complete. Winsock performs an alertable wait in this situation, which can be interrupted by an asynchronous procedure call (APC) scheduled on the same thread, and thereby create unspecified results. Do not issue blocking Winsock function calls without being certain that the current thread is not waiting inside another blocking Winsock function call; doing so results in unpredictable behavior.

The flags parameter can be used to influence the behavior of the function invocation beyond the options specified for the associated socket. The semantics of this function are determined by the socket options and the flags parameter. The latter is constructed by using the bitwise OR operator with any of the following values.

Value Meaning

MSG_PEEK Peeks at the incoming data. The data is copied into the buffer, but is not removed from the input queue. The function subsequently returns the amount of data that can be read in a single call to the recv (or recvfrom) function, which may not be the same as the total amount of data queued on the socket. The amount of data that can actually be read in a single call to the recv (or recvfrom) function is limited to the data size written in the send or sendto function call.

MSG_OOB Processes Out Of Band (OOB) data.

MSG_WAITALL The receive request will complete only when one of the following events occurs:

The buffer supplied by the caller is completely full.

The connection has been closed.

The request has been canceled.

Note that if the underlying transport does not support MSG_WAITALL, or if the socket is in a non-blocking mode, then this call will fail with WSAEOPNOTSUPP. Also, if MSG_WAITALL is specified along with MSG_OOB, MSG_PEEK, or MSG_PARTIAL, then this call will fail with WSAEOPNOTSUPP. This flag is not supported on datagram sockets or message-oriented CO sockets.