For the record, someone who understands Java serialization better than me has come up with a very reasonable way to make GeneratedMessage and GeneratedMessageLite implement Serializable, so that should end up in the next release. Unfortunately DynamicMessage will still not implement Serializable since it would be tricky to do efficiently in the case of many DynamicMessages having the same or overlapping types, and I don't think this is a use case people really need.
On Fri, Feb 12, 2010 at 2:32 AM, yahro <[email protected]> wrote: > Hi, > > Is there something preventing Protocol Buffer Java classes from being > serializable e.g. using java.io.Externalizable? I would like to use > Protocol Buffer classes to store data in caches, data stores etc. > Currently I have to write awkward custom serializers while it seems, > that it would be enough to add add two methods, implement > java.io.Externalizable interface and classes would be efficiently > serializable. Am I missing something? > > Best regards, > Jarek > > -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<protobuf%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/protobuf?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
