Protocol Buffers aren't really designed for over-the-Internet APIs. Unless I'm mistaken, I don't believe that Google allows third-party interaction with their services over Protocol Buffers.
On Mon, Mar 2, 2009 at 19:37, Abraham Williams <[email protected]> wrote: > There is always json. > Perhaps Twitter will consider implementing Protocol Buffers. > Google uses this lightweight protocol > internally: http://code.google.com/p/protobuf/ > I don't know how it compares to json performance wise though. > On Mon, Mar 2, 2009 at 19:14, Jeffrey Greenberg <[email protected]> > wrote: >> >> My app (tweettronics.com) fetches friends and followers for a given >> user with the following pair of calls, done one immediately after the >> other: >> http://twitter.com/friends/ids.xml >> http://twitter.com/followers/ids.xml >> >> They take quite a while on large users (understandably up to a 2-3megs >> of data via XML encoding), but worse they often fail with a 502 error. >> >> It's easy to see on user barackobama and less frequently as you go >> down the top 10 lists... e.g. on ev ... somewhere around 200k >> followers it's less frequent >> >> Can this be addressed on your side? >> >> BTW: I want this data pretty fresh and I'd like to avoid duplicating >> the Twitter DB, so I'm wanting to avoid caching these calls... still I >> can imagine caching as viable just to improve the performance of >> transferring the large ist Nonetheless, since you are deep into >> facing massive data growth, I'm wondering if there are any interesting >> alternatives to a scheme that transfers something other than XML, one >> that pack more data/byte?.... >> >> Thanks >> Jeffrey >> >> http://www.jeffrey-greenberg.com >> >> >> >> >> > > > > -- > Abraham Williams | http://the.hackerconundrum.com > Web608 | Community Evangelist | http://web608.org > This email is: [ ] blogable [x] ask first [ ] private. > Sent from: Madison Wisconsin United States. -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
