Actually, I've dealt with non-participation in client-server applications myself, in the case of client-server applications involving a persistent sign-on, with a distinct thread dedicated to each signed-on client: what happens if a client abends, locks up, or is physically disconnected? The solution I adopted is for the server thread to terminate if a specified amount of time passes without a request from its client, and the client, if signed-on but idle, to periodically send a no-op request to the server, to ensure that this timeout never happens so long as the client remains healthy.
🌷
Actually, I've dealt with non-participation in client-server applications myself, in the case of client-server applications involving a persistent sign-on, with a distinct thread dedicated to each signed-on client: what happens if a client abends, locks up, or is physically disconnected? The solution I adopted is for the server thread to terminate if a specified amount of time passes without a request from its client, and the client, if signed-on but idle, to periodically send a no-op request to the server, to ensure that this timeout never happens so long as the client remains healthy.