Re: My interpersonal communication protocol/style is the most like...

[b10m]

UDP! Who needs handshakes? Just yell ...

[allolex]

I also chose UDP, but I was thinking more abstractly because I send out a lot of data but don't wait for a confirmation... =)

[zakzebrowski]

I also chose UDP, but my thinking was because I tend not to acknowledge communications unless necessary. Also, my communications seem to get dropped often because I've been told to "speak up"... ;)

[parv]

Now that you put it that way, i want to change my vote from SMTP to UDP.

[Beechbone]

And I tend to implement the ack logic in my own way---send the information, resend it packed up another way twice and the request some ack for some random bits of that bunch... ;)

Cannot to that with TCP, so UDP is for me.

[{NULE}]

UDP isn't really like yelling (unless you toss UDP packets at the broadcast address). It's more like writing a note to someone, sticking a dart through it, then throwing the dart at the recipient, covering your ears and running away. For this very reason it made my short list of favorites.

However I ended up voting for SOAP (actually for it's simpler cousin, XMLRPC - being a closet Python and Java hacker (uh oh - here comes the --) means XMLRPC is more widely implemented than SOAP and simplifies interoperability). I've been playing with it some recently, and it is a really simple way to move information without worrying about the busy work or complexity of other solutions. It's also neat to build XMLRPC handlers into your existing Perl/CGI or mod_perl scripts and suddenly get all kinds of new worlds of functionality out of them.

Of course this also merits a nod to HTTP, FTP, SMTP and those other protocols that you can run SOAP/XMLRPC on top of.