Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Protocol Buffers Handbook

You're reading from   Protocol Buffers Handbook Getting deeper into Protobuf internals and its usage

Arrow left icon
Product type Paperback
Published in Apr 2024
Publisher Packt
ISBN-13 9781805124672
Length 226 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Clément Jean Clément Jean
Author Profile Icon Clément Jean
Clément Jean
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Chapter 1: Serialization Primer FREE CHAPTER 2. Chapter 2: Protobuf is a Language 3. Chapter 3: Describing Data with Protobuf Text Format 4. Chapter 4: The Protobuf Compiler 5. Chapter 5: Serialization Internals 6. Chapter 6: Schema Evolution over Time 7. Chapter 7: Implementing the Address Book in Go 8. Chapter 8: Implementing the Address Book in Python 9. Chapter 9: Developing a Protoc Plugin in Golang 10. Chapter 10: Advanced Build 11. Index 12. Other Books You May Enjoy

Quiz

Answer the following questions to test your knowledge of this chapter:

  1. What is backward compatibility?
    1. The ability to interact with newer versions of our app
    2. The ability to interact with older versions of our app
  2. What is forward compatibility?
    1. The ability to interact with newer versions of our app
    2. The ability to interact with older versions of our app
  3. Would there be any backward compatibility problem if, instead of changing the field type from uint32 to uint64, we were changing from uint64 to uint32?
    1. Yes, we might have an overflow
    2. No, all uint32 values are included in uint64
  4. Would there be any forward compatibility problem if, instead of changing the field type from uint32 to uint64, we were changing from uint64 to uint32?
    1. Yes, we might have an overflow
    2. No, all uint32 values are included in uint64
  5. What could potentially happen if we changed a field type from int32 to uint64 (hint: think in both forward and backward compatibility terms)?
    1. Negative values will be encoded...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image