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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@exmulti.com>) id 1UXEvL-0008U8-2t
for bitcoin-development@lists.sourceforge.net;
Tue, 30 Apr 2013 18:05:07 +0000
X-ACL-Warn:
Received: from mail-pa0-f42.google.com ([209.85.220.42])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UXEvJ-0001eY-31
for bitcoin-development@lists.sourceforge.net;
Tue, 30 Apr 2013 18:05:06 +0000
Received: by mail-pa0-f42.google.com with SMTP id kl13so483748pab.29
for <bitcoin-development@lists.sourceforge.net>;
Tue, 30 Apr 2013 11:04:59 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:x-received:x-originating-ip:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type:x-gm-message-state;
bh=wLdwS0zy42RHcWVWaWXLr9aloXDvLy1ZCGg6fNfmhyM=;
b=op9H0/0HY06uoS3YBzRgk59znl1o8geBmyQvpRXdKLoIY3KK5kbrzu4NkCbNPuM4sA
BQacfUM2aBa7viMmMMLf2aFXMN36m1tWOG8XjcxKE8is9SeicnZ4L8qn93K+VLOyClyG
FaLH6coeNCnY1dRzPqWErE1CcVpkyklWJFAOic+uRt7aAuv+y1+7Pfca0a8Uwhu9BK3n
TRzeaC+vWn9vbEs8qd7lcSYLkZSDyc+ItVo95dUHIqX9iYee5g4gAydu9+Ng5gJvc+4b
D8LzK/eoXmVmuz6EZTBPA6xmfElulLXQb/V4mQ3H2Ee80pwb+KTxuuOSklhuLUAL+EYa
3gxQ==
MIME-Version: 1.0
X-Received: by 10.68.231.65 with SMTP id te1mr12062068pbc.98.1367345099084;
Tue, 30 Apr 2013 11:04:59 -0700 (PDT)
Received: by 10.68.240.106 with HTTP; Tue, 30 Apr 2013 11:04:59 -0700 (PDT)
X-Originating-IP: [65.190.215.219]
In-Reply-To: <CAFBxzACmpODv-zvDb39TBpydSinwQ__BaPJfoVBeg==m7RLwrA@mail.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>
Date: Tue, 30 Apr 2013 14:04:59 -0400
Message-ID: <CA+8xBpcoTRfp=HFs4PdWAx1k_bZKRfopcTgeUpjPWSHRXv5qUA@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: "Rebroad (sourceforge)" <rebroad+sourceforge.net@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQkharM8N7rs8nhJNlNkI7Kjfyh6QplSmZ1pz29h+czqIpqPyx8GO7kaBt4vIlsz1ZVgw7Hz
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1UXEvJ-0001eY-31
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: 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 18:05:07 -0000
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.
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.
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.
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.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
|
