Yes, that is already on my list of things I really, really want it to do. It
will inevitably be in "v2" at some point, but to repeat your point: this
will be 100% implementation specific and not generically portable between
platforms, so it will have to be by explicit "opt in".
On 1 February 2011 02:49, NYCBrit <tristra...@googlemail.com> wrote:
> Would it be possible to support recursive graphs in protobuf-net, as a
> implementation-specific custom message extension? For example, if
> protobuf-net could automatically insert an "optional int32 uniqueID =
> 1000" field in to each message, it could store an auto-generated
> unique identifier for each object. Then, if you come across a
> previously serialized object, you need only read/write the uniqueID
> field and leave the other optional fields blank. The protobuf-net
> deserializer could output the previously constructed object. The
> uniqueIDs would only be valid for a defined scope, eg. one contiguous
> wire message.
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> 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