We're fully aware of what Protocol Buffers are their intended use. We use Thrift, Facebook's clone of Protocol Buffers. You might note the use of the world "internal" in the material you quoted.
On Tue, Mar 3, 2009 at 12:05, Dossy Shiobara <[email protected]> wrote: > > On 3/3/09 2:51 PM, Alex Payne wrote: >> >> 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. > > From the Protocol Buffers project page: > > "Protocol Buffers are a way of encoding structured data in an efficient yet > extensible format. Google uses Protocol Buffers for almost all of its > internal RPC protocols and file formats." > > Protocol Buffers are definitely well-designed for over-the-Internet APIs. > It's a means of encoding structured data, like XML is, but efficient. > > XML and JSON are swell, but they suck for any non-trivial amount of data > where the structure's overhead really starts to add up. > > -- > Dossy Shiobara | [email protected] | http://dossy.org/ > Panoptic Computer Network | http://panoptic.com/ > "He realized the fastest way to change is to laugh at your own > folly -- then you can let go and quickly move on." (p. 70) > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
