Much stronger but of limited use still, for the reasons you listed. You very rarely care that the remote tcp/ip stack has acked the message, you care that the

Much stronger but of limited use still, for the reasons you listed. You very rarely care that the remote tcp/ip stack has acked the message, you care that the messages has been received by the program and processed - You're better off implementing your own acks in those cases, allowing you to report back any errors in that ack as well. Or you don't really care, and can just fire and forget those messages. And that also allows you to implement a system where you can pipeline messages - waiting for remote acks when allowing just 1 message in flight limits your throughput severely.