Here's some links for inspiration:
I don't know what prompted this question but I'm curious to see people's responses.
+4
A:
XMPP - The basis of Google Wave. Details at http://www.waveprotocol.org/draft-protocol-spec
AutomatedTester
2009-08-06 17:57:21
XMPP's been used prior to google wave for jabber, you know.
bdonlan
2009-08-06 18:05:05
yea I know but I like it for that reason :)
AutomatedTester
2009-08-07 07:04:50
A:
I like SIP. It is simple, the specs are completely open, and there are a multitude of libraries for every platform/language imaginable. Advanced voice features can now be integrated into any application. And in the bad old days, you had to pay big bucks for a fancy PBX system, where today you can build your own with tools like Asterisk (and many others), and they are fully extensible and programmable. Just like people extend web servers by writing web applications, they are starting to extend SIP/telephony to support voice applications (without having to pay an arm and a leg).
Adam Batkin
2009-08-06 17:58:24
Can't say I'm a fan on SIP. Doesn't play nice with NATs (at least didn't when I was working with it a few years ago).
illvm
2009-08-06 18:05:05
+4
A:
Does anyone really get "excited" about protocols or standards? Perhaps "interested" or even "involved", but "excited"? Do people wake up in the night yelling "Yes!!! [insert your protocol here]!". I don't think so.
anon
2009-08-06 18:03:42
Just the other night, I woke up, sat straight up in bed, and screamed "FTTTTTTTTTTTTPPPPPPPPPPPPPPPPPPPPPPPPPPP!"
Thomas Owens
2009-08-06 18:13:16
@ire_and_curses Well, the insertion would only be performed using a protected method, in accordance with OOP best-ptactice.
anon
2009-08-06 18:18:36
A:
As we move to the cloud and web-services become more pervasive, I think security and privacy are going to become more and more important. For this reason, I vote for SSL.
Umsd
2009-08-06 18:08:47