On Mar 16, 9:59 pm, Caleb wrote:
> Here are the results of a reasonably faithful port of Jon's Java
> benchmark code to C++. I'll see if I can post the code to the "Files"
> section of the Google Group.
Well, I can't do that, but this is probably better:
http://github.com/Bklyn/protobuf/tree/
On Mar 5, 7:07 am, Jon Skeet wrote:
> This is only an initial cut, but I wanted to get it out into the
> community quickly rather than polishing build scripts etc. You
> currently have to build by hand, but there are instructions in the
> readme.
Here are the results of a reasonably faithful po
I have logged this on the protobuf-net site:
http://code.google.com/p/protobuf-net/issues/detail?id=50
Marc Gravell
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, sen
> If it is helpful, I can zip it up and someone the class set.
Please; if it is reproducible, could you send me a sample?
Marc Gravell (protobuf-net)
marc.grav...@gmail.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Gr
That is what I meant.
Another option would be to define a custom option which identifies the
fields of your message that should only be sent to one of the clients, and
then write a reflection-based routine which recursively clears all such
fields in a message. But personally I think having multipl
> edan: Sorry, protocol buffers doesn't provide any magic solution here.
> Maybe you could separate your message into two messages, one which only
> contains data that both clients want, and one with the rest?
>
>
Hm... I don't see how to separate cleanly given that part of my problem is
in the
On Mon, Mar 16, 2009 at 12:12 PM, Jeremy Leader wrote:
>
> I believe you can concatenate two (serialized) messages together,
> yielding a message with all the fields from both messages.
>
> So if all your fields are optional, you could create one instance of
> your message with just the fields co
I believe you can concatenate two (serialized) messages together,
yielding a message with all the fields from both messages.
So if all your fields are optional, you could create one instance of
your message with just the fields common to both clients, and another
instance with just the fields
I have kind of a funny requirement that I was hoping protobuf might support
in an elegant fashion:
I have a message that I want to sent to 2 different clients. They want
mostly the same stuff, but there are a few fields that can be fairly large,
that I only want to send to one of the clients, and
I am using the CompactFramework 3.5 version of protobuf-net and
debugging in the Arm emulator. We have an abstract Message class with
50 child classes. So our Message class has 50 ProtoInclude attributes
on it defining all direct child classes. And all public properties in
the parent and childr
10 matches
Mail list logo
