credit: fortunefundingalliance

My technical background is in computer networking. I spent my twenties studying network protocols, designing queueing systems, and working on security issues. It was a great experience that is still useful today, 20 years later, now that everyone uses that Internet thing.

One principle of networking protocols is the idea of guaranteed delivery versus nonguaranteed. Basically, when you send a message over the Internet, it is broken up into tiny pieces, called packets, and sent down the line, mixed up with all sorts of other packets, and finally reassembled into a message on the other end.

With nonguaranteed delivery, the message is just sent out, and the sender doesn't really know if it got there (believe it or not, there are good applications for this). With guaranteed delivery, by contrast, the receiver sends an acknowledgement (or "ack") to the sender saying, in essence, "I got your message, thanks."

The "TCP" in TCP/IP is a guaranteed delivery protocol.

I was thinking about this because I am doing less computer networking these days and more personal networking. Emailing, Twittering, spending time on the phone. And the "ack" concept works just as well here. (Another metaphor for an ack is a "handshake." I like that one.)

Email, to me, is a nonguaranteed delivery protocol. From a technical standpoint, that's nonsense--Simple Mail Transport Protocol (SMTP), of course, sends acknowledgements to your mail server when your message is delivered. But I'm talking about personal communication.

by: John Caddell

read more

Posted by: Loïc LAMY

Posted on: levidepoches.fr/contagiousideas

Source: futurelab

 

credit: fortunefundingalliance

My technical background is in computer networking. I spent my twenties studying network protocols, designing queueing systems, and working on security issues. It was a great experience that is still useful today, 20 years later, now that everyone uses that Internet thing.