Ok, I understood. Keepalive starts sending probes after some period on _inactivity_. So, if we are still trying to send data after network break, keepalive doesn't work. Keepalive is not suitable for this situation...
> I was tried that solution too and SO_KEEPALIVE flag with other > keepalive flags works only if connection closes and user does nothing > with application. > I added the following lines to function tcp_connect: > > int i = 1; > setsockopt(tcp->sock, SOL_SOCKET, SO_KEEPALIVE, &i, sizeof(int)); > setsockopt(tcp->sock, SOL_TCP, TCP_KEEPCNT, &i, sizeof(int)); > i = 10; > setsockopt(tcp->sock, SOL_TCP, TCP_KEEPIDLE, &i, sizeof(int)); > i = 10; > setsockopt(tcp->sock, SOL_TCP, TCP_KEEPINTVL, &i, sizeof(int)); > > and if i broke connection and do nothing with application (i mean > moving mouse, pressing keys on keyboard) keepalive tiomeout brokes > connection correctly. And if we have some data to send from our input > devices keepalive never works. Maybe i'm doing something wrong? > My client OS is CentOS. ------------------------------------------------------------------------------ What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d _______________________________________________ Freerdp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freerdp-devel
