Hi All,
maybe one of you already faced such problem.
I'd like to activate the %SO_KEEPALIVE socket option while opening a socket, in order to have the operating system TCP stack check if a opened onnection is still alive automatically.
In my case I cannot simply solve the problem of dead peer detection with just sending some request to the other party and timeout for the answer (i.e. a sort of TCP "ping") cause the other device I'm communicating prevents this.
In "classical" C sockets programming I'd be setting the %SO_KEEPALIVE option, but Powerbasic (luckly and unluckly in this case) masks the Winsock2 programming hurdles.
Any ideas?
O'course, if possible, I'd like to avoid implementing from "scratch" the equivalent of Powerbasic TCP OPEN & Co. routines with plain Winsock2 API calls.
))
Thanks for your time and help
Best regards,
Angelo Amoruso
maybe one of you already faced such problem.
I'd like to activate the %SO_KEEPALIVE socket option while opening a socket, in order to have the operating system TCP stack check if a opened onnection is still alive automatically.
In my case I cannot simply solve the problem of dead peer detection with just sending some request to the other party and timeout for the answer (i.e. a sort of TCP "ping") cause the other device I'm communicating prevents this.
In "classical" C sockets programming I'd be setting the %SO_KEEPALIVE option, but Powerbasic (luckly and unluckly in this case) masks the Winsock2 programming hurdles.
Any ideas?
O'course, if possible, I'd like to avoid implementing from "scratch" the equivalent of Powerbasic TCP OPEN & Co. routines with plain Winsock2 API calls.

Thanks for your time and help
Best regards,
Angelo Amoruso
Comment