Hi.
I'll answer my silly question myself, May be it will helo someone in the
future.
The protobuf doesn't take care of frame fragmantation.
Tcp/ip might (and would when data size grow, as was in my case) fragmant
the serialized data into several packets.
If you try to deserialize a partial
Hi.
I'll answer my silly question myself, May be it will helo someone in the
future.
The protobuf doesn't take care of frame fragmantation.
Tcp/ip might (and would when data size grow, as was in my case) fragmant
the serialized data into several packets.
If you try to deserialize a partial
In package com.google.protobuf are errors:
- in Descriptors.java not found import
com.google.protobuf.DescriptorProtos.*;
- in AbstractMessage, DynamicMessage, ExtensionRegistry, TextFormat - is
error field.getContainingType().getOptions()
--
You received this message because you are
This looks to be protobuf-net specific. Note that protobuf-net includes
SerializeWithLengthPrefix and DeserializeWithLengthPrefix which can be used
to simplify working with multiple separate logical messages on a single
stream (such as against a socket), without ever over-reading.
Also - it
Am 21.04.2014 um 17:11 schrieb proto...@googlecode.com:
Comment #11 on issue 434 by tom.ritc...@gmail.com: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while child
still exists: causes segmentation fault
http://code.google.com/p/protobuf/issues/detail?id=434
