[protobuf] Re: "Person" example can not deserialize on iOS 6.1 Simulator.

2013-06-20 Thread Joel Holveck
You may want to check the result from SerializeToOstream. In particular, I note that you didn't set the name field, which is marked as required in addressbook.proto. (I'm assuming that's what you're using.) Without all required fields set, SerializeToOstream will fail. -- You received this

[protobuf] Re: Sanity Check for Protocol buffers

2013-06-20 Thread Joel Holveck
If you want to extend Protobuf, then rather than writing a new parser, I would suggest that you use Protobuf's existing facility for custom options on FieldDescriptorProto. See the description in https://developers.google.com/protocol-buffers/docs/proto#options , under "Custom Options". You c

[protobuf] Issue 523 in protobuf: Python setup.py install --preifx doesn't work

2013-06-20 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 523 by gerry.st...@gmail.com: Python setup.py install --preifx doesn't work http://code.google.com/p/protobuf/issues/detail?id=523 What steps will reproduce the problem? 1. python setup.py build 2. python setu

[protobuf] Re: Issue 522 in protobuf: some doubts using protobuf on iOS

2013-06-20 Thread protobuf
Updates: Status: Invalid Comment #1 on issue 522 by xiaof...@google.com: some doubts using protobuf on iOS http://code.google.com/p/protobuf/issues/detail?id=522 Yes, you need to build it yourself. It won't cross build for a different platform all by itself. -- You received this m

[protobuf] encoding question

2013-06-20 Thread Sébastien Muscat
Hi, I've got an encoding question about the following proto : message Property { required string key = 1; optional string value = 2; } message SysDate { required uint64 sec = 1; required uint32 usec = 2; } message BuiltInTest { required uint32 bit = 1; required uint32 bit_status =

[protobuf] encoding question

2013-06-20 Thread Sébastien Muscat
Hi, I've got an encoding question about the following proto : message Property { required string key = 1; optional string value = 2; } message SysDate { required uint64 sec = 1; required uint32 usec = 2; } message BuiltInTest { required uint32 bit = 1; required uint32 bit_status =

Re: [protobuf] encoding question

2013-06-20 Thread Feng Xiao
On Thu, Jun 20, 2013 at 2:13 AM, Sébastien Muscat wrote: > Hi, > > I've got an encoding question about the following proto : > > message Property { > required string key = 1; > optional string value = 2; > } > > message SysDate { > required uint64 sec = 1; > required uint32 usec = 2; > } >

[protobuf] ZeroCopyInputStream and ZeroCopyOutputStream for socket file descriptors

2013-06-20 Thread adam
I'm working on a C++ application that receives protocol buffers over a network socket. This seems like a core use case of Protobuf, but surprisingly most of the example C++ code I've found when googling about this has not been great. I've seen several examples of people reading from the socket

[protobuf] Re: Issue 522 in protobuf: some doubts using protobuf on iOS

2013-06-20 Thread protobuf
Comment #2 on issue 522 by vance79...@gmail.com: some doubts using protobuf on iOS http://code.google.com/p/protobuf/issues/detail?id=522 thanks.I got it �� 2013-6-21��1:16�� proto...@googlecode.com �� -- You received this message because this project is configured to send all issue