All, I hadn't gotten the chance to look at this before, and it is interesting. Twitter now has another take on a message-streaming API over HTTP, using what looks like a non-HTTP-1.1-compliant form of request pipelining (sending multiple responses over a single open connection). See the documentation at http://apiwiki.twitter.com/Streaming-API-Documentation
This is not what we are doing currently. I'd describe our current API design as more of a delta-queue approach, while Twitter's design is more of a true stream-over-HTTP. Food for thought. Ethan
