I've tried changing the default of the field to -1.
Without rebuilding the Messages, re-reading them with the new
definitions simply gives me the following:
has_uploadlimit = false; uploadlimit= -1.
Since this is the case, I assume that the field in the Message itself
isn't initialized, and that
My messages are stored in a file whose format is
(4Bytes)(Message Length Bytes).
I read the file sequentially, reading the relevant amount of bytes
every iteration, and provide this char* to the ParseMessageFromArray
function.
I also tried using the ParseMessageFromIstream (and provided the
files
Will
http://google-maven-repository.googlecode.com/svn/repository/com/google/protobuf/protobuf-java/be
updated?
Thanks
On Wed, Aug 12, 2009 at 9:49 AM, Kenton Varda wrote:
> Documentation updates have also been submitted and will be live in an hour
> or two.
>
>
> On Tue, Aug 11, 2009 at 6:46 P
Hi,
As is known to lots of people, std::string performs not good for such
reasons as copy-on-write,... etc.
So in my own system i have my own string utilities replaced all
std::string. How could i serialize my own string using protocol
buffer?
Of course i can convert my own string into std::string
Documentation updates have also been submitted and will be live in an hour
or two.
On Tue, Aug 11, 2009 at 6:46 PM, Kenton Varda wrote:
> http://code.google.com/p/protobuf/downloads/list
>
> 2009-08-11 version 2.2.0:
>
> C++
> * Lite mode: The "optimize_for = LITE_RUNTIME" option causes the
http://code.google.com/p/protobuf/downloads/list
2009-08-11 version 2.2.0:
C++
* Lite mode: The "optimize_for = LITE_RUNTIME" option causes the compiler
to generate code which only depends libprotobuf-lite, which is much smaller
than libprotobuf but lacks descriptors, reflection, an
You can certainly POST the protobuf bytes to a url just like any other
data. Of course, your server will need to know about the message type
if you expect it to be able to do anything with the bytes.
Here's an example of using protobuf and HTTP with JAX-RS:
http://www.javarants.com/2008/12/27/us
> Does protocol buffer support Visual studio 2008
Just to add (since VS2008 is a huge beast, supporting a fleet of
languages etc); if you are using C#, then protobuf-net provides
"custom tool" support for .proto in VS2008:
http://marcgravell.blogspot.com/2009/07/protobuf-net-now-with-added-orcas.
In your C++ code, are you storing the message as a NUL-terminated string
(i.e. as char*)? Protocol Buffers are arbitrary byte arrays and may contain
NULs, so this won't work. You must either store the message in a
std::string or you must keep track of the length of the message separately.
On Tue
On Tue, Aug 11, 2009 at 9:36 AM, Peter Keen wrote:
>
> If I understand the docs correctly has_* will return false if the
> value is the same as the default, which in the case of numbers
> defaults to 0.
That is not correct. has_* returns true if the value was explicitly set,
false if not, regar
Yes, MSVC projects are located in the "vsprojects" folder in the source code
distribution.
On Tue, Aug 11, 2009 at 9:50 AM, Shri wrote:
>
> Does protocol buffer support Visual studio 2008
>
> Thanks
> Shridhar
> >
>
--~--~-~--~~~---~--~~
You received this message
Does protocol buffer support Visual studio 2008
Thanks
Shridhar
--~--~-~--~~~---~--~~
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
If I understand the docs correctly has_* will return false if the
value is the same as the default, which in the case of numbers
defaults to 0.
--Pete
On Tuesday, August 11, 2009, multijon wrote:
>
> Hi,
>
> I'm seeing a strange behaviour of the protobuf library in the
> following situation:
>
Hi,
I'm seeing a strange behaviour of the protobuf library in the
following situation:
I have a message which contains an optional field uint32
'uploadLimit'.
I have created and serialized a message containing the value 0 in this
field.
When reading this message in Python and C#, I have the val
14 matches
Mail list logo
