[protobuf] Issue 205 in protobuf: Invalid strings are delivered to application

Status: New Owner: ken...@google.com Labels: Type-Defect Priority-Medium New issue 205 by ngollan: Invalid strings are delivered to application http://code.google.com/p/protobuf/issues/detail?id=205 What steps will reproduce the problem? 1. Have a field of type "string" 2. Fill field with invali

[protobuf] Re: Issue 138 in protobuf: Maven Protoc Plugin fails when a jar file contains a .proto file.

Comment #2 on issue 138 by akbertram: Maven Protoc Plugin fails when a jar file contains a .proto file. http://code.google.com/p/protobuf/issues/detail?id=138 There is an additional bug on the windows platform, where the jar name includes a drive letter, leading to temp folders like: C:\t

[protobuf] Re: Issue 81 in protobuf: Maven Protoc Plugin Code Review

Comment #18 on issue 81 by akbertram: Maven Protoc Plugin Code Review http://code.google.com/p/protobuf/issues/detail?id=81 Can we merge into the trunk in time for release 2.3.1 ? Here is a patch that merges this the maven-plugin branch into r344 and fixes issues #138 and #149 and #152 Plea

[protobuf] Re: Issue 138 in protobuf: Maven Protoc Plugin fails when a jar file contains a .proto file.

Comment #3 on issue 138 by rktoo...@gmail.com: Maven Protoc Plugin fails when a jar file contains a .proto file. http://code.google.com/p/protobuf/issues/detail?id=138 That was Issue 152, which I filed, and it was a very easy fix. Thanks for posting the patch, akbertram. -- You received

[protobuf] Re: Issue 205 in protobuf: Invalid strings are delivered to application

Updates: Status: WorkingAsIntended Comment #1 on issue 205 by temporal: Invalid strings are delivered to application http://code.google.com/p/protobuf/issues/detail?id=205 For performance reasons, we don't bother validating UTF-8 in opt mode (when NDEBUG is defined), leaving it up t

[protobuf] Re: Issue 205 in protobuf: Invalid strings are delivered to application

Comment #2 on issue 205 by ken...@google.com: Invalid strings are delivered to application http://code.google.com/p/protobuf/issues/detail?id=205 For performance reasons, we don't bother validating UTF-8 in opt mode (when NDEBUG is defined), leaving it up to the app. In debug mode, we prin

[protobuf] Re: Issue 204 in protobuf: Message Field Inheritance

That gets a little messy. What I started with was: message A { optional int32 field_a = 1; } message B { optional int32 field_b = 1; optional A sub_a = 2; } Right off the bat that has a couple artifacts that I don't like. B is really a subclass of A, but to refer to A's members I have to

[protobuf] Protobuf as generic marshalling layer

Hi, I want to use protobuf as a generic marshalling mechanism and I'm having some issues with the unmarshalling part, because I need knowledge of what needs to be unmarshalled, i.e. in Java, access to static parseFrom method in target class, which makes it hard to use it in a generic way. A hacky

[protobuf] Protobuf for client/server messaging?

We're currently looking at using protobuf for communication between a number of clients (java and iPhone) and a java server but I'm a bit confused how to best implement our protocol. Our protocol consists of a big number of possible messages but I can't seem to find a way for protobuf to help me d

[protobuf] Re: Issue 204 in protobuf: Message Field Inheritance

That gets a little messy. What I started with was: message A { optional int32 field_a = 1; } message B { optional int32 field_b = 1; optional A sub_a = 2; } Right off the bat that has a couple artifacts that I don't like. B is really a subclass of A, but to refer to A's members I have to

Re: [protobuf] Protobuf for client/server messaging?

On Wed, Jul 14, 2010 at 1:36 AM, bwp wrote: > Our protocol consists of a big number of possible messages but I can't > seem to find a way for protobuf to help me decide which message was > sent. > Writing and parsing messages is really easy when I know what exact > message is being sent but this w

Re: [protobuf] Protobuf for client/server messaging?

On Jul 14, 2010, at 4:36 , bwp wrote: If we have to go down that route what would be a good identifier? See Peter's email. But you can also use msg.getDescriptorForType().getFullName() to get a unique string for each protocol buffer message type. This is what I do for my own RPC system, w

[protobuf] Why do field default values not get serialised?

I am new and want to understand the purpose/usage of default values in the .proto file. E.g: test { optional string a 1 [default ="test"]; } When I create a message object and read the field value, the default will be displayed: test thing; cout

Re: [protobuf] Why do field default values not get serialised?

On Wed, Jul 14, 2010 at 1:47 PM, mark.t.macdon...@googlemail.com < mark.t.macdon...@googlemail.com> wrote: > I am new and want to understand the purpose/usage of default values in > the .proto file. E.g: > > test > { > optional string a 1 [default ="test"]; > } > > When I create a message object

[protobuf] Design advice: variability (at runtime) on the number of fields in a message

Let's assume I'm designing a distributed (client-server) application. The server owns a bunch of parameters. The client (GUI) is to be periodically updated when any of their values change. I could: i) send a small wire message containing one field each time it changes ii) periodically send a big

Re: [protobuf] Design advice: variability (at runtime) on the number of fields in a message

On Wed, Jul 14, 2010 at 14:19, mark.t.macdon...@googlemail.com wrote: > Let's assume I'm designing a distributed (client-server) application. > The server owns a bunch of parameters. The client (GUI) is to be > periodically updated when any of their values change. > > I could: > > i) send a small

Re: [protobuf] Protobuf as generic marshalling layer

On Tue, Jul 13, 2010 at 1:38 AM, Galder Zamarreno wrote: > Hi, > > I want to use protobuf as a generic marshalling mechanism and I'm > having some issues with the unmarshalling part, because I need > knowledge of what needs to be unmarshalled, i.e. in Java, access to > static parseFrom method in t