You'll have to stick some sort of one-byte tag on the front of the message
to identify which type it is.

On Fri, Sep 19, 2008 at 11:05 AM, BeamMeUpScotty <[EMAIL PROTECTED]>wrote:

>
> We're looking at a scenario where there could possibly be many
> different messages on the same wire.  For example, DeviceA and DeviceB
> communicate with a PC.  Both DeviceA and DeviceB use the same
> functional network, and they also use different Proto messages.  The
> question that we're wrestling with is how does the PC differentiate
> between the different Proto implementations?  I've done tests using
> the generated Python sources and looked at the serialized messages.
> (btw, we're VERY concerned with wire format size)  Looks like if I
> have multiple messages in the same proto, there's no way that I can
> tell the difference between them from looking at the wire format.  We
> could nest the messages, but this adds a bytes to the implementation.
> Is there another way?
>
> Scott Pavetti
> >
>

--~--~---------~--~----~------------~-------~--~----~
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 from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/protobuf?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to