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
Message from discussion Number of Bits Written to Memory

Received: by 10.14.53.2 with SMTP id f2mr369605eec.17.1298399819992;
        Tue, 22 Feb 2011 10:36:59 -0800 (PST)
X-BeenThere: protobuf@googlegroups.com
Received: by 10.14.125.11 with SMTP id y11ls8126eeh.0.p; Tue, 22 Feb 2011
 10:36:54 -0800 (PST)
Received: by 10.14.53.65 with SMTP id f41mr386324eec.6.1298398859219;
        Tue, 22 Feb 2011 10:20:59 -0800 (PST)
Received: by 10.14.53.65 with SMTP id f41mr386323eec.6.1298398859194;
        Tue, 22 Feb 2011 10:20:59 -0800 (PST)
Return-Path: <ken...@google.com>
Received: from smtp-out.google.com (hpaq8.eem.corp.google.com [172.25.149.8])
        by gmr-mx.google.com with ESMTPS id p52si2066792eeh.3.2011.02.22.10.20.59
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 22 Feb 2011 10:20:59 -0800 (PST)
Received-SPF: pass (google.com: domain of ken...@google.com designates 172.25.149.8 as permitted sender)
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ken...@google.com designates 172.25.149.8 as permitted sender) smtp.mail=ken...@google.com; dkim=pass (test mode) header...@google.com
Received: from kpbe18.cbf.corp.google.com (kpbe18.cbf.corp.google.com [172.25.105.82])
	by smtp-out.google.com with ESMTP id p1MIKwDU001433
	for <protobuf@googlegroups.com>; Tue, 22 Feb 2011 10:20:58 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta;
	t=1298398858; bh=ZNkBK6GovNFx+bLLC9Bb2C4Atlw=;
	h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject:
	 To:Cc:Content-Type;
	b=M1kNctwX0bArVnhgGwq7ynqBG7JyI/YNQwIfIAHj8es0nYVSRg4zgJ2ZTao6Ka6wa
	 9bT8C8eEOIWSdPLcW/RrA==
Received: from qwd7 (qwd7.prod.google.com [10.241.193.199])
	by kpbe18.cbf.corp.google.com with ESMTP id p1MIKuKC018540
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT)
	for <protobuf@googlegroups.com>; Tue, 22 Feb 2011 10:20:57 -0800
Received: by qwd7 with SMTP id 7so3108826qwd.19
        for <protobuf@googlegroups.com>; Tue, 22 Feb 2011 10:20:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=beta;
        h=domainkey-signature:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:cc:content-type;
        bh=aBMnHT15xZMNgasqxDe03YlXs3F+uWXxooyB7UOMSvs=;
        b=JTaUy/e+yUi7D6MHRtwgJrXvfCMPY5zjByDg+lkvxURhNLLeZoNgFs7+wyUBZqH5Cl
         vyXe1g2C7RDAFN1umtuQ==
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=google.com; s=beta;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        b=sYyaDWI9vlrA48N01Wq67ftosh4hwTUuuAiuR3yIadiV1RSmdY/Yr+os3/ec1HJg5j
         4rouGRSUwO1lk1e6u6zw==
Received: by 10.229.79.12 with SMTP id n12mr2298043qck.129.1298398856148; Tue,
 22 Feb 2011 10:20:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.111.228 with HTTP; Tue, 22 Feb 2011 10:20:26 -0800 (PST)
In-Reply-To: <852cd990-549b-42ba-a458-be13f189e...@n36g2000pre.googlegroups.com>
References: <852cd990-549b-42ba-a458-be13f189e...@n36g2000pre.googlegroups.com>
From: Kenton Varda <ken...@google.com>
Date: Tue, 22 Feb 2011 10:20:26 -0800
Message-ID: <AANLkTimy=95g85QmPGTQbjqD_EtTMi6rgo3+YV96P...@mail.gmail.com>
Subject: Re: [protobuf] Number of Bits Written to Memory
To: Tanya <turtle...@gmail.com>
Cc: Protocol Buffers <protobuf@googlegroups.com>
Content-Type: multipart/alternative; boundary=00163646d92498f6c3049ce30ab7
X-System-Of-Record: true

--00163646d92498f6c3049ce30ab7
Content-Type: text/plain; charset=ISO-8859-1

Protobufs provide their own encoding.  You can't control exactly how the
bytes are written, unless you write your own encoder, which would defeat the
purpose.

On Thu, Feb 3, 2011 at 8:58 AM, Tanya <turtle...@gmail.com> wrote:

> Hi, we are looking at replacing a XML/JAXB project with something
> similar to protocol buffers, especially since it's multi-platform, but
> there are a couple of concerns we have seen that would prevent us from
> switching. I'd like to verify that what we think is actually true
> before passing on what seems to be a very cool solution Google has
> come up with.
>
> My main question revolves around how the bytes are stored. In our
> current solution, we store by bit, so some items have very strange
> amounts of bits being stored (i.e. 5 bits, 14 bits). We noticed that
> protocol buffers seem to only store by byte or word (very even amounts
> of bits) and have a unique way of encoding.
>
> Basically, we need some way of specifying how the bytes are encoded/
> written to memory, and we need to specify the number of bits written
> each time. Is this possible to do in protocol buffers? And if so, how
> would it be accomplished?
>
> Thanks. Any help is greatly appreciated.
>
> --
> 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
> protobuf+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/protobuf?hl=en.
>
>

--00163646d92498f6c3049ce30ab7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Protobufs provide their own encoding. =A0You can&#39;t control exactly how =
the bytes are written, unless you write your own encoder, which would defea=
t the purpose.<br><br><div class=3D"gmail_quote">On Thu, Feb 3, 2011 at 8:5=
8 AM, Tanya <span dir=3D"ltr">&lt;<a href=3D"mailto:turtle...@gmail.com">tu=
rtle...@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Hi, we are looking at replacing a XML/JAXB =
project with something<br>
similar to protocol buffers, especially since it&#39;s multi-platform, but<=
br>
there are a couple of concerns we have seen that would prevent us from<br>
switching. I&#39;d like to verify that what we think is actually true<br>
before passing on what seems to be a very cool solution Google has<br>
come up with.<br>
<br>
My main question revolves around how the bytes are stored. In our<br>
current solution, we store by bit, so some items have very strange<br>
amounts of bits being stored (i.e. 5 bits, 14 bits). We noticed that<br>
protocol buffers seem to only store by byte or word (very even amounts<br>
of bits) and have a unique way of encoding.<br>
<br>
Basically, we need some way of specifying how the bytes are encoded/<br>
written to memory, and we need to specify the number of bits written<br>
each time. Is this possible to do in protocol buffers? And if so, how<br>
would it be accomplished?<br>
<br>
Thanks. Any help is greatly appreciated.<br>
<font color=3D"#888888"><br>
--<br>
You received this message because you are subscribed to the Google Groups &=
quot;Protocol Buffers&quot; group.<br>
To post to this group, send email to <a href=3D"mailto:protobuf@googlegroup=
s.com">protobuf@googlegroups.com</a>.<br>
To unsubscribe from this group, send email to <a href=3D"mailto:protobuf%2B=
unsubscribe@googlegroups.com">protobuf+unsubscribe@googlegroups.com</a>.<br=
>
For more options, visit this group at <a href=3D"http://groups.google.com/g=
roup/protobuf?hl=3Den" target=3D"_blank">http://groups.google.com/group/pro=
tobuf?hl=3Den</a>.<br>
<br>
</font></blockquote></div><br>

--00163646d92498f6c3049ce30ab7--