I actually don't know. You'd have to try compiling it and running the tests
and tell me what happens.
On Mon, Nov 10, 2008 at 9:43 PM, mpprasad <[EMAIL PROTECTED]> wrote:
>
> Is the Protocol Buffers supports WinCE platform?
>
> Thanks
> Prasad.
> >
>
--~--~-~--~~~---
On Tue, Nov 11, 2008 at 10:41 AM, Kenton Varda <[EMAIL PROTECTED]> wrote:
> Either blah.ByteSize() or blah.size() would be valid things to use.
>
I mean, message.ByteSize() or str.size().
--~--~-~--~~~---~--~~
You received this message because you are subscribed t
On Tue, Nov 11, 2008 at 7:46 AM, ChJees <[EMAIL PROTECTED]> wrote:
> I managed to solve my problem now. I used the blah.Bytesize() function
> instead of sizeof( blah.c_str() ) when sending the message size :3.
Ah, yes, don't use c_str() with serialized protobufs because they may
contain zeros be
I managed to solve my problem now. I used the blah.Bytesize() function
instead of sizeof( blah.c_str() ) when sending the message size :3.
Someone should really add to documentation about Sending and Receiving
info between Server and Clients to prevent further Headaches. (Not
small ones either!)
I have no idea about the core C++ etc impementations - but if it
helps, protobuf-net builds for .NET CF 2.0 and .NET CF 3.5, if that is
any help. Note that there isn't an RPC stack for this yet, but I'm
working on it.
Marc
--~--~-~--~~~---~--~~
You received this me
