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
|
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 <sirk390@gmail.com>) id 1SINIR-00054i-Ud
for bitcoin-development@lists.sourceforge.net;
Thu, 12 Apr 2012 16:54:59 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.175 as permitted sender)
client-ip=209.85.213.175; envelope-from=sirk390@gmail.com;
helo=mail-yx0-f175.google.com;
Received: from mail-yx0-f175.google.com ([209.85.213.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1SINIO-00040L-4w
for bitcoin-development@lists.sourceforge.net;
Thu, 12 Apr 2012 16:54:59 +0000
Received: by yenm3 with SMTP id m3so1459372yen.34
for <bitcoin-development@lists.sourceforge.net>;
Thu, 12 Apr 2012 09:54:50 -0700 (PDT)
Received: by 10.60.14.166 with SMTP id q6mr4048983oec.17.1334249690606; Thu,
12 Apr 2012 09:54:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.13.103 with HTTP; Thu, 12 Apr 2012 09:54:29 -0700 (PDT)
In-Reply-To: <CA+XhJbq01knW4XizF3DjaaXnzChvixsxwgFMzWiPPehYuvVk1w@mail.gmail.com>
References: <CA+XhJbpNYUyPm2Ymcpg3grbfGnfERCsUJNJuByEJbJLsMMmMbQ@mail.gmail.com>
<CABsx9T029cY-OJfZ9n-rSZc7i36e+CkOZPZixdi8EFL7oN4jhQ@mail.gmail.com>
<20120412160151.GA1100@vps7135.xlshosting.net>
<CA+XhJbq01knW4XizF3DjaaXnzChvixsxwgFMzWiPPehYuvVk1w@mail.gmail.com>
From: Christian Bodt <sirk390@gmail.com>
Date: Thu, 12 Apr 2012 18:54:29 +0200
Message-ID: <CA+XhJboPopi-Wbg3u4mYsSDxD4CuM_Mu2vCcekaKWw_mL=C2uw@mail.gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=e89a8ff25142d9ad7304bd7e3639
X-Spam-Score: -0.3 (/)
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
(sirk390[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (sirk390[at]gmail.com)
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: 1SINIO-00040L-4w
Subject: Re: [Bitcoin-development] Adding request/reply id in messages
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: sirk390@gmail.com
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: Thu, 12 Apr 2012 16:55:00 -0000
--e89a8ff25142d9ad7304bd7e3639
Content-Type: text/plain; charset=UTF-8
> For example, doing a second
> identical "getblocks" request will not result in more "inv" replies, as
> the client
> prevents retransmits.
Yes, the current prototype implementation modifies that. "getblocks" always
results in one "inv" with [0-500] elements.
It also removes the filtering on previously transmitted block invs.
see patch:
https://github.com/sirk390/bitcoin/commit/17a27e3d56efa107697b53c193364a33951f1dd1
--e89a8ff25142d9ad7304bd7e3639
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<br><div class=3D"gmail_quote"><div class=3D"gmail_quote"><div class=3D"im"=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">For example, doing a second<br>
identical "getblocks" request will not result in more "inv&q=
uot; replies, as the client<br>
prevents retransmits. </blockquote><div><br></div></div><div>Yes, the curre=
nt prototype implementation modifies that. "getblocks" always res=
ults in one "inv" with [0-500] elements.</div><div>It also remove=
s the filtering on previously transmitted block invs. =C2=A0</div>
<div>see patch:=C2=A0<a href=3D"https://github.com/sirk390/bitcoin/commit/1=
7a27e3d56efa107697b53c193364a33951f1dd1" target=3D"_blank">https://github.c=
om/sirk390/bitcoin/commit/17a27e3d56efa107697b53c193364a33951f1dd1</a>
</div><div><br></div><div><br></div></div>
</div><br>
--e89a8ff25142d9ad7304bd7e3639--
|
