Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <rebroad@gmail.com>) id 1UXDDB-0005P0-SQ for bitcoin-development@lists.sourceforge.net; Tue, 30 Apr 2013 16:15:25 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.171 as permitted sender) client-ip=209.85.223.171; envelope-from=rebroad@gmail.com; helo=mail-ie0-f171.google.com; Received: from mail-ie0-f171.google.com ([209.85.223.171]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UXDD8-0000eb-B7 for bitcoin-development@lists.sourceforge.net; Tue, 30 Apr 2013 16:15:25 +0000 Received: by mail-ie0-f171.google.com with SMTP id e11so850762iej.30 for <bitcoin-development@lists.sourceforge.net>; Tue, 30 Apr 2013 09:15:17 -0700 (PDT) X-Received: by 10.50.12.201 with SMTP id a9mr11192874igc.10.1367338517114; Tue, 30 Apr 2013 09:15:17 -0700 (PDT) MIME-Version: 1.0 Sender: rebroad@gmail.com Received: by 10.64.23.47 with HTTP; Tue, 30 Apr 2013 09:14:56 -0700 (PDT) In-Reply-To: <CAFBxzACw=G7UgG853zQrM-Z1-B4VqSQR5YUJQ5n1=wnv7EyWsw@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> From: "Rebroad (sourceforge)" <rebroad+sourceforge.net@gmail.com> Date: Tue, 30 Apr 2013 23:14:56 +0700 X-Google-Sender-Auth: yOt0WW3On5tpMTOjZbLyeTL5ylk Message-ID: <CAFBxzACmpODv-zvDb39TBpydSinwQ__BaPJfoVBeg==m7RLwrA@mail.gmail.com> To: "bitcoin-development@lists.sourceforge.net" <bitcoin-development@lists.sourceforge.net> Content-Type: multipart/alternative; boundary=14dae93409b599b78c04db964ee1 X-Spam-Score: -0.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 (rebroad[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1UXDD8-0000eb-B7 Subject: [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 16:15:26 -0000 --14dae93409b599b78c04db964ee1 Content-Type: text/plain; charset=ISO-8859-1 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. --14dae93409b599b78c04db964ee1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">As part of a roadmap for block downloading, I think this m= ay be a good time to look into providing an HTTP/HTTPS protocol for block d= ownloading - this would also allow web proxies to cache blocks and thus mak= e it more accessible, as well as cater for resumeable downloads.</div> --14dae93409b599b78c04db964ee1--