Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Protocol Buffers
Home
+ new post
About this group
Join this group
Message from discussion encoding of embedded messages and repeated elements
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
etorri  
View profile  
 More options Jun 23 2009, 1:37 pm
From: etorri <e...@torri.be>
Date: Tue, 23 Jun 2009 10:37:39 -0700 (PDT)
Local: Tues, Jun 23 2009 1:37 pm
Subject: Re: encoding of embedded messages and repeated elements
Print | View thread | Show original | Report this message | Find messages by this author

ok thanks. it is as it is.

(just looking at the feasibility of implementing the PB in Ada for my
own projects :-)

On Jun 23, 6:17 pm, Alek Storm <alek.st...@gmail.com> wrote:

> Hi etorri,

> Embedded messages and strings have the exact same wire format.  When parsing
> a message, it's impossible to know whether you're parsing one or the other,
> and since strings have to be encoded using their length in bytes, we can't
> do something different for embedded messages.

> Cheers,
> Alek

> On Tue, Jun 23, 2009 at 9:06 AM, etorri <e...@torri.be> wrote:

> > Hello,

> > The "length delimited" encoding basically tells that the following N
> > bytes belong to this field. Wouldn't it be easier to instead use the
> > number of elements that belong to the embedded message (repeated
> > element).

> > Now (as far as I have understood) the message needs to be built from
> > fragments and then collected together as the lengths are not known
> > beforehand and it would be expensive to calculate the byte-length of
> > the embedded message.

> > Instead, it would be relatively inexpensive to calculate just the
> > number of following elements that make the embedded message before
> > starting to encode it.

> > This would enable streaming of PB or encoding and sending the elements
> > right as they are encoded.

> > Sorry if I misunderstood something. I have just started looking at BP.

> --
> Alek Storm


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google