I initially was try to get Protocol Buffers to work from Java to C++
over sockets. I am still unsure how to do this but I decided to try
and test to see if I could get a Java to Java version working over
sockets and was successful. However, I was experiencing a weirdness
which might be causing
On Oct 21, 2010, at 1:21 , Kevin wrote:
Basically, the code that receives the data will wait until the stream
is closed before reading the data. I thought that flushing the data
would cause the data to be sent but that apparently has no effect. Is
this my implementation or a problem with using
Mozy has just open sourced their implementation of Protocol Buffers
for Ruby. The implementation has been in use internally at Mozy for
over a year. This implementation has put a lot of focus on
serialization/deserialization performance, and completeness.
The ruby protobuf compiler calls out to
Updates:
Status: WorkingAsIntended
Comment #3 on issue 227 by ken...@google.com: /usr/lib/libprotobuf.so.6:
undefined symbol: pthread_once
http://code.google.com/p/protobuf/issues/detail?id=227
(No comment was entered for this change.)
--
You received this message because you are
I have seemed to fix the reading issues on the C++ and Java sides and
it is working as expected.
My only concern now is in regards to messages sizes and the prepending
the size at the beginning. What is the best way to go about this? My
test message required on one byte but my next messages
