What I think is also interesting is how Twitter documents this new API. maybe we can use this as an example.
What are the advantages of our method vs. their method? Or are there basic philosophical differences? D. On Tue, Nov 24, 2009 at 4:33 PM, Ethan Jewett <[email protected]> wrote: > 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 >
