Hi, UNIX: A timer thread regularily polls all established connections, testing with kill(pid, 0). If a remote connection was established, polling uses the process id of the server process responsible for transmitting socket request/answers. If running out of connections, this polling is executed too. NT: Similar, but WaitForSingleObject( pUserCommCtrl->hClientProcess, 0) != WAIT_TIMEOUT instead of kill is used.
CU jrg > -----Original Message----- > From: Flemming Frandsen [mailto:[EMAIL PROTECTED]] > Sent: Donnerstag, 31. Januar 2002 10:12 > To: [EMAIL PROTECTED] > Subject: Failed client detection > > > How does sapdb detect that a client has failed? > > Does it keep an eye on the process to see if it's still alive? > > -- > Regards Flemming Frandsen aka. Dion/Swamp http://dion.swamp.dk > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
