Is it possible to send user data in CSocket::Connect
-
I hope client can send some secure data at connect time vs CSocket::Connect, so that server can read the data and knows it is my client connection, or server rejects the connection immediately. Is it possible to send user data vs CSocket::Connect?
-
I hope client can send some secure data at connect time vs CSocket::Connect, so that server can read the data and knows it is my client connection, or server rejects the connection immediately. Is it possible to send user data vs CSocket::Connect?
includeh10 wrote:
Is it possible to send user data vs CSocket::Connect?
Don't think so - I think authentication (for that's what you want) has to be done separately post-connect.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
-
I hope client can send some secure data at connect time vs CSocket::Connect, so that server can read the data and knows it is my client connection, or server rejects the connection immediately. Is it possible to send user data vs CSocket::Connect?
includeh10 wrote:
I hope client can send some secure data at connect time vs CSocket::Connect
In order to send and receive data during a connect operation you will need to use WSAConnect() rather than CSocket::Connect(). Keep in mind this is protocol dependent and is not supported by the TCP/IP stack.
1300 calories of pure beef goodness can't be wrong!
-
includeh10 wrote:
I hope client can send some secure data at connect time vs CSocket::Connect
In order to send and receive data during a connect operation you will need to use WSAConnect() rather than CSocket::Connect(). Keep in mind this is protocol dependent and is not supported by the TCP/IP stack.
1300 calories of pure beef goodness can't be wrong!
-
I hope client can send some secure data at connect time vs CSocket::Connect, so that server can read the data and knows it is my client connection, or server rejects the connection immediately. Is it possible to send user data vs CSocket::Connect?
from the msdn about WSAConnect: The lpCallerData parameter contains a pointer to any user data that is to be sent along with the connection request (called connect data). This is additional data, not in the normal network data stream, that is sent with network requests to establish a connection. This option is used by legacy protocols such as DECNet, OSI TP4, and others. Note Connect data is not supported by the TCP/IP protocol in Windows. Connect data is supported only on ATM (RAWWAN) over a raw socket.
it's my pleasure to make friend with you.
-
Note Connect data is supported only on ATM (RAWWAN) over a raw socket. TCP/IP in Windows does not support connect data.
it's my pleasure to make friend with you.
zhu_lin wrote:
Connect data is supported only on ATM (RAWWAN) over a raw socket
Which would make it protocol dependent.
zhu_lin wrote:
TCP/IP in Windows does not support connect data.
echo...echo...echo...
1300 calories of pure beef goodness can't be wrong!
-
I hope client can send some secure data at connect time vs CSocket::Connect, so that server can read the data and knows it is my client connection, or server rejects the connection immediately. Is it possible to send user data vs CSocket::Connect?
Hello, You cannot do such a thing. Any validation should be done after accepting the connection only.
It is a crappy thing, but it's life -^ Carlo Pallini
-
I hope client can send some secure data at connect time vs CSocket::Connect, so that server can read the data and knows it is my client connection, or server rejects the connection immediately. Is it possible to send user data vs CSocket::Connect?