You only need to register the extensions that you want to use. Unknown
extensions will get preserved as unknown fields (at least in the C++ and
Java implementations; python does not support unknown fields), and when you
reserialize the message those will be included. The registered receivers
will need to have ExtensionRegistry's to parse the extensions they care
about. Netty would need to provide a hook for them to provide the
On Tue, Nov 15, 2011 at 10:05 AM, Neil Gendzwill <ngendzw...@yahoo.com>wrote:
> New to protobuf but my google-fu is failing me here. I would like to
> write a receiver that parses a base message, then distributes it to
> registered receivers who know how to parse the extensions. I don't want the
> receiver to know about the extensions, other than the range defined in the
> base .proto. From reading the docs, you can define extensions to a message
> in separate .proto files. But it seems like the receiver would need to
> know about all the extensions via an ExtensionRegistry. This is to be used
> along with Netty - another user is dealing with a similar thing shown
> Is there a way around this? A code example, ideally in Java?
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To view this discussion on the web visit
> To post to this group, send email to email@example.com.
> To unsubscribe from this group, send email to
> For more options, visit this group at
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to firstname.lastname@example.org.
To unsubscribe from this group, send email to
For more options, visit this group at