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 Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

Received: by 10.42.118.1 with SMTP id v1mr12493207icq.17.1349826175800;
        Tue, 09 Oct 2012 16:42:55 -0700 (PDT)
X-BeenThere: nodejs@googlegroups.com
Received: by 10.42.91.75 with SMTP id o11ls16741976icm.2.gmail; Tue, 09 Oct
 2012 16:42:43 -0700 (PDT)
Received: by 10.50.42.225 with SMTP id r1mr2078946igl.1.1349826163401;
        Tue, 09 Oct 2012 16:42:43 -0700 (PDT)
Received: by 10.50.42.225 with SMTP id r1mr2078945igl.1.1349826163382;
        Tue, 09 Oct 2012 16:42:43 -0700 (PDT)
Return-Path: <lordma...@gmail.com>
Received: from mail-ie0-f171.google.com (mail-ie0-f171.google.com [209.85.223.171])
        by gmr-mx.google.com with ESMTPS id s15si1881285igi.1.2012.10.09.16.42.43
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 09 Oct 2012 16:42:43 -0700 (PDT)
Received-SPF: pass (google.com: domain of lordma...@gmail.com designates 209.85.223.171 as permitted sender) client-ip=209.85.223.171;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of lordma...@gmail.com designates 209.85.223.171 as permitted sender) smtp.mail=lordma...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-ie0-f171.google.com with SMTP id s9so17046114iec.16
        for <nodejs@googlegroups.com>; Tue, 09 Oct 2012 16:42:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=EQ9AIn9KFnNEFPP8PjxLYgO3JToiy+jU9zZKMMjDkcA=;
        b=dV91kGoCul+Z+jM4u1eFzSRAQyn7RnxuHyZ2iqSe3y5unLGbDQStobVzsqlmSUxi+v
         fPDPU0hrRZPWGzgPMTQFmORDl2Qe20N18o5/3xcN/KF9uXlF2EppJ1UICaz6oJ2I6qhN
         MHeXJ4zlIt8YOQk6gGT/R+ksEgZF1oATHQFRqrx26HJWpEmPMYFgBnBQlSgXRQYw6rv/
         atl1vB8DN0w4xVwO1VwyY8A1RhZKyNn+BSeHWW8HKUxM5mi1tvjQsY0ngfSbOSnLuZCU
         GSsJzKj1EPu9kn9sesop3est672DksdY6JQpj9zDHzVBEgquHpnN07p7rXKjP+kTcuPl
         pGXg==
MIME-Version: 1.0
Received: by 10.50.216.234 with SMTP id ot10mr3422896igc.71.1349826163245;
 Tue, 09 Oct 2012 16:42:43 -0700 (PDT)
Received: by 10.50.168.73 with HTTP; Tue, 9 Oct 2012 16:42:43 -0700 (PDT)
In-Reply-To: <b01df81e-63e4-4422-a2f7-5420aa9b9...@n2g2000yqn.googlegroups.com>
References: <CADcwD-GuAEG=EZ2ZF029H2RKpWbzkCdCCcsb47VeKrFpiAS...@mail.gmail.com>
	<b9dde6a3-be23-4300-a3dc-5d4adfbba07a@googlegroups.com>
	<CADcwD-GGpFiOPsOdJYEVw-NU1=fYrJpUF_605=wNuMbiOLb...@mail.gmail.com>
	<CABe_6ekLTGno789w1iu4ib7khQi1d0kncPD-weSge5VenQt...@mail.gmail.com>
	<b01df81e-63e4-4422-a2f7-5420aa9b9...@n2g2000yqn.googlegroups.com>
Date: Tue, 9 Oct 2012 19:42:43 -0400
Message-ID: <CA+CQ935ycA6ATey-_URyP62pC2U_pM5h0w-U9kcW8fHDdPA...@mail.gmail.com>
Subject: Re: [nodejs] Re: Poll for v0.10 feature: Crypto default to 'binary'
 strings vs defaulting to buffers
From: Stewart Mckinney <lordma...@gmail.com>
To: nodejs@googlegroups.com
Content-Type: multipart/alternative; boundary=f46d040167a9f800bc04cba8e4f0

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

my vote is a), go for it

On Tue, Oct 9, 2012 at 7:32 PM, mscdex <msc...@gmail.com> wrote:

> On Oct 9, 6:21 pm, codepilot Account <codepi...@gmail.com> wrote:
> > Just out of curiosity, will this be the last nail in the coffin of
> 'binary'
> > encoding? At least as the default, I mean.
>
> As a default, I'd hope so.
>
> Last nail in the coffin totally though? I'd hope not. This particular
> discussion (eliminating this encoding altogether) has been had on the
> list here and on node's github issues almost ad nauseum, but I am
> still in favor of keeping it around (with a note discouraging its use
> in the docs) until Buffer's core capabilities are equivalent or nearly
> equivalent to those of strings (e.g. indexOf, lastIndexOf, etc).
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>

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

my vote is a), go for it<br><br><div class=3D"gmail_quote">On Tue, Oct 9, 2=
012 at 7:32 PM, mscdex <span dir=3D"ltr">&lt;<a href=3D"mailto:mscdex@gmail=
.com" target=3D"_blank">msc...@gmail.com</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">
<div class=3D"im">On Oct 9, 6:21=A0pm, codepilot Account &lt;<a href=3D"mai=
lto:codepi...@gmail.com">codepi...@gmail.com</a>&gt; wrote:<br>
&gt; Just out of curiosity, will this be the last nail in the coffin of &#3=
9;binary&#39;<br>
&gt; encoding? At least as the default, I mean.<br>
<br>
</div>As a default, I&#39;d hope so.<br>
<br>
Last nail in the coffin totally though? I&#39;d hope not. This particular<b=
r>
discussion (eliminating this encoding altogether) has been had on the<br>
list here and on node&#39;s github issues almost ad nauseum, but I am<br>
still in favor of keeping it around (with a note discouraging its use<br>
in the docs) until Buffer&#39;s core capabilities are equivalent or nearly<=
br>
equivalent to those of strings (e.g. indexOf, lastIndexOf, etc).<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
--<br>
Job Board: <a href=3D"http://jobs.nodejs.org/" target=3D"_blank">http://job=
s.nodejs.org/</a><br>
Posting guidelines: <a href=3D"https://github.com/joyent/node/wiki/Mailing-=
List-Posting-Guidelines" target=3D"_blank">https://github.com/joyent/node/w=
iki/Mailing-List-Posting-Guidelines</a><br>
You received this message because you are subscribed to the Google<br>
Groups &quot;nodejs&quot; group.<br>
To post to this group, send email to <a href=3D"mailto:nodejs@googlegroups.=
com">nodejs@googlegroups.com</a><br>
To unsubscribe from this group, send email to<br>
<a href=3D"mailto:nodejs%2Bunsubscribe@googlegroups.com">nodejs+unsubscribe=
@googlegroups.com</a><br>
For more options, visit this group at<br>
<a href=3D"http://groups.google.com/group/nodejs?hl=3Den?hl=3Den" target=3D=
"_blank">http://groups.google.com/group/nodejs?hl=3Den?hl=3Den</a><br>
</div></div></blockquote></div><br>

--f46d040167a9f800bc04cba8e4f0--