Yes, the typical architectural reply to using ping as a keep alive is "no way, don't do it". There's probably a reason they put the sessions to sleep.
On a note aside, I worked on a project once where the wireless connections were not working well. This forced intermittent drops in a scanning application the entire warehouse was using. The network folks, being who they were "Nope we don't see any issues" made the developer put in a keep alive pinger.
Can you believe that? When I caught wind of this problem, (having been a network engineer in the past) I brought this up to the Network Team in a joint team meeting discussing issues. They about ran me out of house and home for insisting it was a network issue. About a month later they sent a chap over to check the infrastructure, sure enough the wireless units were mounted behind metal shelving stacks, and had in general very poor installations. Once they cleaned all that up, everything worked great. The only problem aftward, in their minds; was that I was still an asshole for challenging them! 😃
Until they fixed it, the developer was on the hook for the failing application! He had come to the end of his rope. As a very accommodating person, he had done everything he was told to do and it's still didn't work, but only he was on the hook.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes, the typical architectural reply to using ping as a keep alive is "no way, don't do it". There's probably a reason they put the sessions to sleep.
On a note aside, I worked on a project once where the wireless connections were not working well. This forced intermittent drops in a scanning application the entire warehouse was using. The network folks, being who they were "Nope we don't see any issues" made the developer put in a keep alive pinger.
Can you believe that? When I caught wind of this problem, (having been a network engineer in the past) I brought this up to the Network Team in a joint team meeting discussing issues. They about ran me out of house and home for insisting it was a network issue. About a month later they sent a chap over to check the infrastructure, sure enough the wireless units were mounted behind metal shelving stacks, and had in general very poor installations. Once they cleaned all that up, everything worked great. The only problem aftward, in their minds; was that I was still an asshole for challenging them! 😃
Until they fixed it, the developer was on the hook for the failing application! He had come to the end of his rope. As a very accommodating person, he had done everything he was told to do and it's still didn't work, but only he was on the hook.