Yes, I was planning to reply on facebook as well. I was a bit surprised, but this could be the reason why 1. It is random2. It is on some networks often, on others rarely or never3. It is for no reason. In all honesty, I always try to keep a socket live with actual CHANGING bytes every 30 seconds. We are running tests now, we limit events on 14 per fbRemoteEvent and we add one NewGuid.ToString() that we fire every minute with a fbBlock if we haven't seen any of those events in the past minute. The results look promising.
> From: j...@cincura.net > To: firebird-net-provider@lists.sourceforge.net > Date: Thu, 18 Jun 2015 05:44:50 +0000 > Subject: [Firebird-net-provider] Keep-alive packets > > Hi *, > > This is what I read just now: > RFC 1122, section 4.2.3.6 indicates that acknowledgements for TCP keepalives > without data may not be transmitted reliably by routers; this may cause valid > connections to be dropped. Furthermore, TCP/IP stacks are not required to > support keepalives at all (and many embedded stacks do not), so this solution > may not translate to other platforms. > > This might explain why still some events (connections) are (sometimes) lost, > even though we use keep-alive on that socket. > > -- > Mgr. Jiří Činčura > Independent IT Specialist > ------------------------------------------------------------------------------ > _______________________________________________ > Firebird-net-provider mailing list > Firebird-net-provider@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
------------------------------------------------------------------------------
_______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
