[chetanahuja]

The answer to that of course is that the underlying network protocols need to be aware of this dilemma. It's wasteful for every developer to try and solve this problem on their own.

The main culprit here is of course TCP's session based view of the world which was invented for a completely different era. An era when "cable got cut" was a catastrophic event that was almost never going to happen. It's a pity that the native app world is still mostly stuck with TCP/HTTP based networking stack where a UDP/mobile-specific-protocol is what's needed.