Socket handles may take any value in the range 0 to INVALID_SOCKET–1.īecause the SOCKET type is unsigned, compiling existing source code from, for example, a UNIX environment may lead to compiler warnings about signed/unsigned data type mismatches. Windows Sockets handles have no restrictions, other than that the value INVALID_SOCKET is not a valid socket. As a result, a socket descriptor on UNIX may be passed to any of the standard file I/O functions (read and write, for example).įurthermore, all handles in UNIX, including socket handles, are small, non-negative integers, and some applications make assumptions that this will be true. In UNIX, a socket descriptor is represented by a standard file descriptor. NET method MySocket.BeginReceive() will return 0 length only when server disconnects or will wait on this method for any other answer.In Winsock applications, a socket descriptor is not a file descriptor and must be used with the Winsock functions. If answer_byte = "\E1" then login suceededĮlse answer_byte= "\E2" then login failed Send_Login & Received_bytes!=0 then is bad login (always fails here on receive) In very short code would be something like this:
Unfortunatelly I have no code for newcamd server, just the code for client in linux which I translated. So there might be few possible issues: I did not received an answer and I get disconected prior this or server did not understood my login (which is less likely but pissible). Console application connects to server and gets response with 14 bytes(as soons as it connects), then I am trying to send login data and then I should get a response from server but I always get 0 length which is not suppost to be like that. I've wrote c++ console application and it uses winsock 2.0.
Sorry for maybe silly question, but I am not familiar with winsock 2.0 and especially in C++, so could anyone help me with this:
0 kommentar(er)
