Hello All,
I have an B4J app that as B4A client connected to it using sockets. If the kill the process using the IDE Kill process button or from windows resource manager the B4A clients cannot detect that the sockets are no longer valid.
If I exit the B4J app and do the formal closing everything is ok. It there a way of detecting the B4J app is being closed I and can formally close the sockets.
The B4A apps send a 'ping packet' every 30 seconds, so, in the meantime I will have to implement some sort of packet ack to overcome this. The B4A app checks the socket state frequently but is always returns a connected state of TRUE.
Any ideas ?
Regards
John.
I have an B4J app that as B4A client connected to it using sockets. If the kill the process using the IDE Kill process button or from windows resource manager the B4A clients cannot detect that the sockets are no longer valid.
If I exit the B4J app and do the formal closing everything is ok. It there a way of detecting the B4J app is being closed I and can formally close the sockets.
The B4A apps send a 'ping packet' every 30 seconds, so, in the meantime I will have to implement some sort of packet ack to overcome this. The B4A app checks the socket state frequently but is always returns a connected state of TRUE.
Any ideas ?
Regards
John.