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
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <bpcamac@gmail.com>) id 1UXGoh-0001Xp-7N
for bitcoin-development@lists.sourceforge.net;
Tue, 30 Apr 2013 20:06:23 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.210.171 as permitted sender)
client-ip=209.85.210.171; envelope-from=bpcamac@gmail.com;
helo=mail-ia0-f171.google.com;
Received: from mail-ia0-f171.google.com ([209.85.210.171])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UXGof-00035g-5C
for bitcoin-development@lists.sourceforge.net;
Tue, 30 Apr 2013 20:06:22 +0000
Received: by mail-ia0-f171.google.com with SMTP id r13so808059iar.16
for <bitcoin-development@lists.sourceforge.net>;
Tue, 30 Apr 2013 13:06:15 -0700 (PDT)
X-Received: by 10.50.77.73 with SMTP id q9mr602398igw.97.1367352375881;
Tue, 30 Apr 2013 13:06:15 -0700 (PDT)
Received: from [10.112.1.14] ([50.7.1.130])
by mx.google.com with ESMTPSA id d4sm24169585igc.3.2013.04.30.13.06.12
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Tue, 30 Apr 2013 13:06:14 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Brenton Camac <bpcamac@gmail.com>
In-Reply-To: <CA+8xBpcoTRfp=HFs4PdWAx1k_bZKRfopcTgeUpjPWSHRXv5qUA@mail.gmail.com>
Date: Tue, 30 Apr 2013 15:06:12 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4EA3A617-AA9D-4E4B-B4CC-AC7BC28B2BB5@gmail.com>
References: <CAPg+sBjSe23eADMxu-1mx0Kg2LGkN+BSNByq0PtZcMxAMh0uTg@mail.gmail.com>
<CANEZrP3FA-5z3gAC1aYbG2EOKM2eDyv7zX3S9+ia2ZJ0LPkKiA@mail.gmail.com>
<CAAS2fgSo6Ua8giSKhYTjGm=2U1nBjprHOBqCL7dSNr9MQX_6tw@mail.gmail.com>
<CAPaL=UUhrb+4CANVB6refCOeQwcf_A80Way_C_oJbDKM9kmWXg@mail.gmail.com>
<CAAS2fgRR3K_dVMhOSHpga91tFaK7G99ouKLFpXHbgxEsvY+_Wg@mail.gmail.com>
<CAPaL=UU8=EzhAni+rRtro4QZdgreUSJxeMpqJai19kGZ9JHTyg@mail.gmail.com>
<20130429035523.GA11611@savin>
<BLU0-SMTP4789CDF0A9814E7D8D2D662C8B20@phx.gbl>
<CAFBxzACw=G7UgG853zQrM-Z1-B4VqSQR5YUJQ5n1=wnv7EyWsw@mail.gmail.com>
<CAFBxzACmpODv-zvDb39TBpydSinwQ__BaPJfoVBeg==m7RLwrA@mail.gmail.com>
<CA+8xBpcoTRfp=HFs4PdWAx1k_bZKRfopcTgeUpjPWSHRXv5qUA@mail.gmail.com>
To: bitcoin-development@lists.sourceforge.net
X-Mailer: Apple Mail (2.1503)
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-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
(bpcamac[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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: 1UXGof-00035g-5C
Subject: Re: [Bitcoin-development] Service bits for pruned nodes
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, 30 Apr 2013 20:06:23 -0000
Sounds like this part of Bitcoin (block sharing) would definitely =
benefit from having a REST (HTTP) API.
REST-based web APIs are a common feature of most online services these =
days. Makes writing other client services so much easier. Plus you get =
the benefit of the HTTP ecosystem for free (HTTP caches, etc).
- Brenton Camac=20
On Apr 30, 2013, at 1:04 PM, Jeff Garzik <jgarzik@exmulti.com> wrote:
> On Tue, Apr 30, 2013 at 12:14 PM, Rebroad (sourceforge)
> <rebroad+sourceforge.net@gmail.com> wrote:
>> As part of a roadmap for block downloading, I think this may be a =
good time
>> to look into providing an HTTP/HTTPS protocol for block downloading - =
this
>> would also allow web proxies to cache blocks and thus make it more
>> accessible, as well as cater for resumeable downloads.
>=20
> Speaking generally, I've always been a supporter of finding new and
> creative ways to store and transmit blocks. The more diversity, the
> less likely bitcoin can be shut down worldwide.
>=20
> HTTP is fine, but you run into many issues with large files. You
> would need a very well defined HTTP-retrievable layout, with proper
> HTTP headers along the entire path, if you want web caches to function
> properly. You need HTTP byte range support, HTTP 1.1 keep-alives, and
> other features for resuming large, interrupted downloads.
>=20
> The format currently used by bitcoind would be just fine --
> blocks/blkNNNN.dat for raw data, size-limited well below 1GB. Just
> need to add a small metadata download, and serve the raw block files.
>=20
> --=20
> Jeff Garzik
> exMULTI, Inc.
> jgarzik@exmulti.com
>=20
> =
--------------------------------------------------------------------------=
----
> Introducing AppDynamics Lite, a free troubleshooting tool for =
Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
|