Hi,
I am trying to receive response from server which a protobuf, which is
encoded, and there are { at the end of string so, I am truncating string
using :
registerAgentResponse_string=registerAgentResponse_string.replace({,);
then I convert this to byteArray using :
Hi Marc,
Could you elaborate on your note: (note: this is specific to protobuf-net,
not protocol buffers more widely)
What are the implications if communicating with non-protobuf-net targets?
(ie. java, python, ... applications)
Joel
On Wednesday, June 20, 2012 9:05:49 AM UTC-4, Marc
The data is of course compatible. A `ListFoo` is directly mappable to
.proto via for example:
message SomeOuterMessage {
repeated Foo items = 1;
}
In fact, for that reason, serializing a ListFoo will produce **exactly**
the same data on the wire as serializing:
On Jun 26, 2012, at 11:08 , d34th4ck3r wrote:
What is it that I am doing wrong?
Protocol buffers are a *binary* format. Those funny characters at the end of
the string are probably part of the message, and you should leave them there.
You also should not be passing them around as strings. They
