OT: @Soli, nice to see you back. Where have you been?
This is an interesting argument that reminds me of the difference between "communication" and "connection," both at a technical level and a human level. Commenter ppietra's points are valid for many networking protocols that support both connected and unconnected messaging, where connected messaging generally infers that there is a notion of session/connection state information that is maintained by the endpoints and intermediaries that exists even when packets are not being actively sent of the wire. This contents, context, lifetime, semantics, and roles related to this state information is protocol specific. That's all fine and good.The human side of this argument falls along the lines of the distinctions drawn between communication and connection that are the primary focus of writers, speakers, and presenters like John C. Maxwell, most notably in his book "Everyone Communicates, Few Connect." I'm not going to rehash the book here, but it is very evident that there's a whole lot of communication taking place around the topic of connections, but not very much connection is actually happening.