K
KK
Guest
Hi,
I have an voip application that uses winsock2. In PC when i do
FD_ISSET for readFds , it returns the read fdset when the socket
connection fails(network cable unplugged) and hence when i try to do a
read operation on the returned set, i get an error.Thus enabling me to
detect the socket failure in PC.
However the same application when run in WinCE device, using the same
Winsock2, does not behave the way mentioned above. I am unable to
detect the socket failure in the WinCE device.
Why is it that the same winsock api behave differently in PC and WinCE
based device though the winsock2 apis are the same ?
Expecting a positive response.
Regards,
Ani
I have an voip application that uses winsock2. In PC when i do
FD_ISSET for readFds , it returns the read fdset when the socket
connection fails(network cable unplugged) and hence when i try to do a
read operation on the returned set, i get an error.Thus enabling me to
detect the socket failure in PC.
However the same application when run in WinCE device, using the same
Winsock2, does not behave the way mentioned above. I am unable to
detect the socket failure in the WinCE device.
Why is it that the same winsock api behave differently in PC and WinCE
based device though the winsock2 apis are the same ?
Expecting a positive response.
Regards,
Ani