[protobuf] Re: Has anyone offered to write a ruby proto compiler, yet?
There are a few Ruby implementations listed at http://code.google.com/p/protobuf/wiki/ThirdPartyAddOns - do any of those fit the bill? On Wednesday, July 18, 2012 4:38:42 PM UTC-7, coyo wrote: > > I'm making no promises, but if someone hasn't offered yet, what I have > seen of protobuf has me very excited! > > I may make this one of my primary projects, to at the very least, write > bindings to the C compiler in ruby, and eventually a pure ruby compiler. > > I intend to use protobuf as the primary serialization format for a P2P > overlay network I've been working on for the last three years. > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To view this discussion on the web visit https://groups.google.com/d/msg/protobuf/-/0MNrKwNbuFcJ. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Has anyone offered to write a ruby proto compiler, yet?
I'm making no promises, but if someone hasn't offered yet, what I have seen of protobuf has me very excited! I may make this one of my primary projects, to at the very least, write bindings to the C compiler in ruby, and eventually a pure ruby compiler. I intend to use protobuf as the primary serialization format for a P2P overlay network I've been working on for the last three years. -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To view this discussion on the web visit https://groups.google.com/d/msg/protobuf/-/f7bcxdI5MuMJ. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
Re: [protobuf] Static allocation
I understand, but if one wants to keep a large persistent message allocated and walk over it frequently, there is a price to pay on cache misses that can be significant. In my situation I am maintaining a large persistent instance of a large message type that I used as a cached data set to compare runtime data with, and if it has changed, I want to re-send the parent message with only the changed bits across the network. This frequent operation can benefit from locality of reference if there was an option to generate the code statically, so that every lookup into the message doesn't have to involve a cache miss. On Tue, Jul 17, 2012 at 1:30 PM, Evan Jones wrote: > On Jul 17, 2012, at 2:33 , Jeremy Swigart wrote: > > Is there a way to tell the proto compiler to generate message > definitions for which the message fields are statically defined rather than > each individual field allocated with dynamic memory? Obviously the repeater > fields couldn't be fully statically allocated(unless you could provide the > compiler with a max size), but it would be preferable to have the option to > create messages with minimal dynamic memory impact. Is this possible in the > current library? > > I'll assume you are talking C++. In this case, if you re-use a single > message, it will re-use the dynamically allocated memory. This means that > after the "maximal" message(s) have been parsed, it will no longer allocate > memory. This is approximately equivalent to what you want. See Optimization > Tips in: > > https://developers.google.com/protocol-buffers/docs/cpptutorial > > Hope that helps, > > Evan > > -- > http://evanjones.ca/ > > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 66 in protobuf: cannot install using easy_install
Comment #51 on issue 66 by a...@northisup.com: cannot install using easy_install http://code.google.com/p/protobuf/issues/detail?id=66 Can somebody update the file at http://protobuf.googlecode.com/files/protobuf-2.4.1.zip? -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Best way to share protocol buffer objects in c++
Hi, I followed the steps in the tutorial and tailor it for my needs. In my case, I have two c++ applications; one for sending messages and other for receiving. I created a proto file to define my object to be exchanged between these two distinct applications. Then, I created my object with protoc tool provided. What I want is to put this generated object class in a separate DLL or lib for enabling the two applications (sender, receiver) to be linked with this DLL to use this shared object for exchanging in between. As this object will be placed in a DLL, AFAIK, I need to export methods in this shared object to let sender and receiver applications to create this object and make calls. What is the best way to achieve this mechanism? I saw there is "--cpp_out=dllexport_decl=__declspec(dllexport)" option for protoc tool to export classes but it does not help for the inherited members, such as method: protoObject.SerializeAsString(). TIA! -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To view this discussion on the web visit https://groups.google.com/d/msg/protobuf/-/rBpRUWksG-gJ. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.