>What is usually not ok is two simultaneous recv()-s or send()-s. >They access the same stream object and any stream is not
>safe for multiple reads or writes.
Does this apply even when you are using the socket in conjuction with a
completion port?
GetQueuedCompletionStatus return ERROR_SUCCESS ... if GetQueuedCompletionStatus return ERROR_SUCCESS, The socket handle ... associated with a completion port is closed. ... Then how do he socket associate with the completion port.I use ...Prev by Date: ... (microsoft.public.win32.programmer.networks)
Re: Socket shutdown fails ... > there is no way to 'disassociate' a handle from the completion port.... >>> connections (hiding the SOCKET API calls from the user). ... >>> When creating outbound connections and then attaching them to the IOCP ... You call shutdown() as before but this time ... (microsoft.public.win32.programmer.networks)
Re: Socket shutdown fails ... How happen if you close completion port before shutdown(),... > connections (hiding the SOCKET API calls from the user). ... > When creating outbound connections and then attaching them to the IOCP ... (microsoft.public.win32.programmer.networks)
Re: Handling thousands of TCP socket connections ... >>reference to the number of IO Completion Port threads being around 1000. ... >>> standard socket.BeginReceive use an IO Completion Port Thread? ... >>> simply call this method for each and every socket I am handling on the ... >>> basis it will call the callback method using the threads in the standard ... (microsoft.public.dotnet.general)
How to wait on completion port and event? ... until data arrives OR a win32 event is signalled. ... I understand how to do this for a normal socket:... WSAEventSelect(mySocket, hNetworkEvent, FD_READ); ... I'd like to achieve something similar for the completion port.... (microsoft.public.win32.programmer.networks)
