Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Protocol Buffers Handbook
  • Table Of Contents Toc
  • Feedback & Rating feedback
Protocol Buffers Handbook

Protocol Buffers Handbook

By : Clément Jean
5 (2)
close
close
Protocol Buffers Handbook

Protocol Buffers Handbook

5 (2)
By: Clément Jean

Overview of this book

Explore how Protocol Buffers (Protobuf) serialize structured data and provides a language-neutral, platform-neutral, and extensible solution. With this guide to mastering Protobuf, you'll build your skills to effectively serialize, transmit, and manage data across diverse platforms and languages. This book will help you enter the world of Protocol Buffers by unraveling the intricate nuances of Protobuf syntax and showing you how to define complex data structures. As you progress, you’ll learn schema evolution, ensuring seamless compatibility as your projects evolve. The book also covers advanced topics such as custom options and plugins, allowing you to tailor validation processes to your specific requirements. You’ll understand how to automate project builds using cutting-edge tools such as Buf and Bazel, streamlining your development workflow. With hands-on projects in Go and Python programming, you’ll learn how to practically apply Protobuf concepts. Later chapters will show you how to integrate data interchange capabilities across different programming languages, enabling efficient collaboration and system interoperability. By the end of this book, you’ll have a solid understanding of Protobuf internals, enabling you to discern when and how to use and redefine your approach to data serialization.
Table of Contents (13 chapters)
close
close

Decoding data to type with --decode

Similarly, we have the --decode flag, which takes a binary and returns the data into text format. Once again, here, this flag is mostly for debugging and, in our case, for learning.

Now, remember that we already did the opposite of decode. This means that we will be able to take the output of encode, redirect it to decode, and we should get our input back. This would look like the following:

input > encode > decode > input

So, let us start with the encode part. We are already familiar with it; we can just execute the following command:

$ cat user.txtpb | protoc --encode=User user.proto

Or, we could execute this command:

$ Get-Content user.txtpb | protoc --encode=User user.proto

We will redirect the standard output of these commands to a file for convenience. We can do this by redirecting to a file, like so:

$ … > user.bin

With that, we can now see how to use --decode. It is very similar to --encode. It takes...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY