1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <chris.double@gmail.com>) id 1V978r-0001En-QT
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Aug 2013 05:27:37 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.180 as permitted sender)
client-ip=209.85.192.180; envelope-from=chris.double@gmail.com;
helo=mail-pd0-f180.google.com;
Received: from mail-pd0-f180.google.com ([209.85.192.180])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1V978q-0006sO-3C
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Aug 2013 05:27:37 +0000
Received: by mail-pd0-f180.google.com with SMTP id y10so4357808pdj.39
for <bitcoin-development@lists.sourceforge.net>;
Mon, 12 Aug 2013 22:27:30 -0700 (PDT)
X-Received: by 10.69.0.168 with SMTP id az8mr2671501pbd.51.1376371650179; Mon,
12 Aug 2013 22:27:30 -0700 (PDT)
MIME-Version: 1.0
Sender: chris.double@gmail.com
Received: by 10.70.45.73 with HTTP; Mon, 12 Aug 2013 22:26:50 -0700 (PDT)
In-Reply-To: <CANEZrP1XYyO0aspJ-A-0+_pRDKrtaHZrNTjfOnxBGX8Beiw2Xw@mail.gmail.com>
References: <B4D8D241-E758-4806-8B12-C9A78BF1470B@grabhive.com>
<CANEZrP2c6nsf2z5_hKDfHdO1HEJ+Y+aoiSdfYPMxK_jzrvLEow@mail.gmail.com>
<54F09675-D6A7-4415-82F1-920248E8188D@grabhive.com>
<CANEZrP24P_m_eWbcs3PJNomG4kFDPUyGE2uQjod9qPmpBS+1mg@mail.gmail.com>
<CANEZrP1XYyO0aspJ-A-0+_pRDKrtaHZrNTjfOnxBGX8Beiw2Xw@mail.gmail.com>
From: Chris Double <chris.double@double.co.nz>
Date: Tue, 13 Aug 2013 17:26:50 +1200
X-Google-Sender-Auth: _z7FLMw0XOs0mOalq52aI0LHvks
Message-ID: <CALn1vHF60qN53ZMk6GZd91xFtcYWBSBY_vNP=qNrqLDj3YvomA@mail.gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [209.85.192.180 listed in list.dnswl.org]
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(chris.double[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1V978q-0006sO-3C
Subject: Re: [Bitcoin-development] SPV client in pure JavaScript?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 05:27:38 -0000
On Sat, Aug 10, 2013 at 12:14 AM, Mike Hearn <mike@plan99.net> wrote:
> Oh, I forgot to make it clear - Chrome apps/extensions can make raw TCP
> socket connections:
>
> http://blog.chromium.org/2012/11/introducing-tcp-listen-new-api-for.html
There's a Raw Sockets proposal at the W3C that provides TCP sockets:
<http://www.w3.org/2012/sysapps/raw-sockets/>
Firefox OS has an API that is being discussed as part of that:
<https://developer.mozilla.org/en-US/docs/WebAPI/TCP_Socket>
So there's a possibility of a standardized approach in the future.
Chris.
--
http://www.bluishcoder.co.nz
|
