Maybe you should move your project to code.google.com? You wouldn't have to
host your SVN on (apparently) your own machine that way.
Anyway, I've added a link to your wiki page.
On Mon, Aug 24, 2009 at 8:09 PM, opticron wrote:
>
> Good news! It looks like I convinced the webmaster to poke at th
Good news! It looks like I convinced the webmaster to poke at the site
and get some pages allowed on HTTP connections. Please try the page
again and let me know if you have issues with it.
On Aug 23, 3:30 pm, Omnifarious wrote:
> On Aug 19, 12:41 am, Marc Gravell wrote:
>
> > The problem is th
cool. thanks Pete. your help is greatly appreciated!
On Aug 24, 4:33 pm, Peter Keen wrote:
> I looked at the protobuf-net source a little bit and it looks like if
> you write the length with WriteLittleEndian32 instead of WriteVarint32
> you should be good to go, as long as you use PrefixStyle
I looked at the protobuf-net source a little bit and it looks like if
you write the length with WriteLittleEndian32 instead of WriteVarint32
you should be good to go, as long as you use PrefixStyle.Fixed32
within the C# call to DeserialzeWithLengthPrefix().
--Pete
On Mon, Aug 24, 2009 at 4:17 PM
On Mon, Aug 24, 2009 at 4:17 PM, Jay Thomas wrote:
>
> This code ideally has to operate with C# code on the other side of the
> socket that uses the DeserializeWithLengthPrefix() method call. The
> message originates in C++ environment on a linux box and terminates in
> C# environment on a window
This code ideally has to operate with C# code on the other side of the
socket that uses the DeserializeWithLengthPrefix() method call. The
message originates in C++ environment on a linux box and terminates in
C# environment on a windows PC. Why doesn't C++ support the same
methods as C#? The o
You sort of have to roll your own. In my project I'm doing something like this:
coded_output->WriteVarint32(message->ByteSize());
message->SerializeToCodedStream(coded_output);
And then on the reading side:
uint32_t size;
if (! coded_input->ReadVarint32(&size)) {
return NULL; // just an examp
Some things I forgot to mention:
-working on Slackware Linux platform
-did text search for DeserializeWithLengthPrefix() and haven't found
any header or code files with this method
-was able to find lots of serializing methods in message.h but that
same header file doesn't contain any methods star
Hello
I am looking for a way to serialize/deserialize with length prefix
under c++. The serialized bytes will sent to a TCP socket. I am
aware that C# has a method SerializeWithLengthPrefix() and
DeserializeWithLengthPrefix(). Are there any such analogous methods
for C++? Please point out any
Thanks, I had no idea about the data method.
Much to learn.
Regards
Saptarshi
On Aug 24, 2009, at 4:09 PM, Kenton Varda wrote:
> Yshould never use .c_str() in this case -- use .data() and .size()
> instead.
>
> On Mon, Aug 24, 2009 at 12:58 PM, Saptarshi Guha > wrote:
> Hello,
> Thank you! Be
Yes, unlike C-style char*, C++'s std::string can store strings that contain
NUL bytes. You should never use .c_str() in this case -- use .data() and
.size() instead.
On Mon, Aug 24, 2009 at 12:58 PM, Saptarshi Guha
wrote:
> Hello,
> Thank you! Being new to c++ i had no idea of the size method. I
Hello,
Thank you! Being new to c++ i had no idea of the size method. I was
thinking of strlen on c_str() which would have given me the wrong
number of bytes.
Nice and clean now.
Regards
Saptarshi
On Mon, Aug 24, 2009 at 3:21 PM, Kenton Varda wrote:
> In C++, "bytes" fields are stored using std::
Generally the most efficient way to serialize a message to stdout is:
message.SerializeToFileDescriptor(STDOUT_FILENO);
(If your system doesn't define STDOUT_FILENO, just use the number 1.)
If you normally use C++'s cout, you might want to write to that instead:
message.SerializeToOstream(st
In C++, "bytes" fields are stored using std::string. This class has a
size() method which returns the length of the string. So, the length of
sdata1 is: message.sdata1().size()
So you want to use option (A).
You would use option B if you wanted to store multiple independent byte
strings, each o
On Aug 24, 7:51 am, Saptarshi wrote:
> Hello,
> Suppose I would like to store a type that could be a sequence of raw
> bytes, so
>
> message ...{
>
> optional bytes sdata1=1; //A
> repeated bytes sdata2=2; //B
> optional BYT sdata3=3; //C
>
> }
>
> messag
BROADBAND REVIEW...BROADBAND REVIEW...BROADBAND REVIEW...
http://internet345.50webs.com/broadband-review.html
http://internet345.50webs.com/broadband-review.html
http://internet345.50webs.com/broadband-review.html
@
--~--~-~--~~~---~
Hello,
Suppose I would like to store a type that could be a sequence of raw
bytes, so
message ...{
optional bytes sdata1=1; //A
repeated bytes sdata2=2; //B
optional BYT sdata3=3; //C
}
message BYT{
uint32 length=1;
bytes data=2;
}
Now I have a unsigned c
17 matches
Mail list logo
