[protobuf] Question about set_allocated_foo/release_foo

2013-03-08 Thread Kevin Regan
I often have situations like this: void do_something(const std::string value) { my_proto_buffer.set_value(value); // serialize my_proto_buffer to a stream } Would it be valid to do this: void do_something(const std::string value) {

[protobuf] Re: Question about set_allocated_foo/release_foo

2013-03-14 Thread Kevin Regan
Giving this a bump. This might also be considered a feature request (the ability to temporarily assign a string value to a protocol buffer during serialization, rather than copying it). --Kevin On Friday, March 8, 2013 1:49:29 PM UTC-8, Kevin Regan wrote: I often have situations like

Re: [protobuf] Re: Question about set_allocated_foo/release_foo

2013-03-14 Thread Kevin Regan
will protobuf support shared_ptr stuff. On Thu, Mar 14, 2013 at 6:17 PM, Kevin Regan kevin@gmail.comjavascript: wrote: Giving this a bump. This might also be considered a feature request (the ability to temporarily assign a string value to a protocol buffer during serialization, rather

Re: [protobuf] Partial Decoding of message

2013-07-08 Thread Kevin Regan
This is how I handle the same issue. This would be similar to most multi-threaded daemons taking client input. The manager reads the message type and passes the socket/stream to a handling thread. On Monday, July 8, 2013 10:59:12 AM UTC-7, Ilia Mirkin wrote: Unfortunately it's not

[protobuf] Simply library for converting between protobuf objects and JsonCpp objects.

2013-07-11 Thread Kevin Regan
on Ubuntu 12.04) that expects the protobuf library and JsonCpp (http://jsoncpp.sourceforge.net/) to be installed in /usr/local. Please let me know what you think and if you have any suggestions. Thanks, Kevin Regan k.re...@emc.com kevin.d.re...@gmail.com -- You received this message because