Protocol Buffers: Google's Data Interchange Format [modified]
-
Check this out protocol buffer XML is used all over the map, from data integration project to the omnipresent web services. And every time we work with XML, discussion on performance and size overhead is guaranteed. Is there anything better than XML? Is it a protocol buffer? As per the Google documentation, protocol buffer is not a replacement for XML. Open Source at Google has done a good job in releasing the protocol buffer documentation. They do have a java tutorial on the open source website. Let us know your take on this data format?
modified on Wednesday, July 9, 2008 2:41 PM
-
Check this out protocol buffer XML is used all over the map, from data integration project to the omnipresent web services. And every time we work with XML, discussion on performance and size overhead is guaranteed. Is there anything better than XML? Is it a protocol buffer? As per the Google documentation, protocol buffer is not a replacement for XML. Open Source at Google has done a good job in releasing the protocol buffer documentation. They do have a java tutorial on the open source website. Let us know your take on this data format?
modified on Wednesday, July 9, 2008 2:41 PM
-
Check this out protocol buffer XML is used all over the map, from data integration project to the omnipresent web services. And every time we work with XML, discussion on performance and size overhead is guaranteed. Is there anything better than XML? Is it a protocol buffer? As per the Google documentation, protocol buffer is not a replacement for XML. Open Source at Google has done a good job in releasing the protocol buffer documentation. They do have a java tutorial on the open source website. Let us know your take on this data format?
modified on Wednesday, July 9, 2008 2:41 PM
Interesting, I wonder why they left out C# code generation. After all, they say it'll compile to a language of your choice! Marc
-
Check this out protocol buffer XML is used all over the map, from data integration project to the omnipresent web services. And every time we work with XML, discussion on performance and size overhead is guaranteed. Is there anything better than XML? Is it a protocol buffer? As per the Google documentation, protocol buffer is not a replacement for XML. Open Source at Google has done a good job in releasing the protocol buffer documentation. They do have a java tutorial on the open source website. Let us know your take on this data format?
modified on Wednesday, July 9, 2008 2:41 PM
The advantages of XML: can be self-describing, plenty of off-the-shelf tools, APIs for working with it. Disadvantages: verbose, verbosity often combated with ridiculously terse syntax requiring schema information to be sent out-of-band anyway. XML is a good default choice, to the extent that any default choice is "good". When something less heavy is desired, alternatives such as JSON are nice for languages that have good text processing support built-in and don't have good binary processing support available. RDF, SOAP, etc. tend to be overkill for nearly everything. This protocol buffer thing sounds like a reasonable way of designing and implementing reasonably light-weight binary protocols. Sure beats whatever MS was smoking when they designed the VIEWSTATE protocols in ASP.NET... (similar though, apart from all the documentation that doesn't exist for the latter)
Citizen 20.1.01
'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
-
Interesting, I wonder why they left out C# code generation. After all, they say it'll compile to a language of your choice! Marc
-
Check this out protocol buffer XML is used all over the map, from data integration project to the omnipresent web services. And every time we work with XML, discussion on performance and size overhead is guaranteed. Is there anything better than XML? Is it a protocol buffer? As per the Google documentation, protocol buffer is not a replacement for XML. Open Source at Google has done a good job in releasing the protocol buffer documentation. They do have a java tutorial on the open source website. Let us know your take on this data format?
modified on Wednesday, July 9, 2008 2:41 PM
I like the look of it - I may well use it at some point...but let's be honest, it's a refactoring of traditional RPC with IDL, extracting the marshalling code generator into a separate application that generates OO code rather than procedural code. Once (If!!!) there's a Haskell code generator, it'll be useful for my current project (Haskell client, Python server-side components, using RESTful 'web services').
-
I like the look of it - I may well use it at some point...but let's be honest, it's a refactoring of traditional RPC with IDL, extracting the marshalling code generator into a separate application that generates OO code rather than procedural code. Once (If!!!) there's a Haskell code generator, it'll be useful for my current project (Haskell client, Python server-side components, using RESTful 'web services').
everything old is new again
-
everything old is new again
Except COBOL - that is (and ever will be) old...
-
Except COBOL - that is (and ever will be) old...
Stuart Dootson wrote:
that is (and ever will be) old...
... and always was.
-
Except COBOL - that is (and ever will be) old...
Stuart Dootson wrote:
Except COBOL - that is (and ever will be) old...
:) Yeah, but consider COBOL was one of the first attempts to make programming computers easy for the masses -- sound familiar?