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
|
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 <mh.in.england@gmail.com>) id 1R0vka-00088D-RK
for bitcoin-development@lists.sourceforge.net;
Tue, 06 Sep 2011 13:31:40 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.175 as permitted sender)
client-ip=209.85.220.175; envelope-from=mh.in.england@gmail.com;
helo=mail-vx0-f175.google.com;
Received: from mail-vx0-f175.google.com ([209.85.220.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1R0vkZ-0004Ly-Rp
for bitcoin-development@lists.sourceforge.net;
Tue, 06 Sep 2011 13:31:40 +0000
Received: by vxj14 with SMTP id 14so6289883vxj.34
for <bitcoin-development@lists.sourceforge.net>;
Tue, 06 Sep 2011 06:31:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.38.99 with SMTP id f3mr4990732vdk.392.1315315894415; Tue,
06 Sep 2011 06:31:34 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.52.157.228 with HTTP; Tue, 6 Sep 2011 06:31:34 -0700 (PDT)
In-Reply-To: <4E661FAE.9020008@gmail.com>
References: <4E65CEE6.7030002@gmail.com> <4E65DA06.9060403@gmail.com>
<CALxbBHUajARXc1oA-NjD+U8hW5uSqF=u4ZHHBfcmT_O8GjpNiA@mail.gmail.com>
<CANEZrP0VXDUs_mAKCVKD1Q0ijyb989oADrCN1zTZ1nnN_JQ=cQ@mail.gmail.com>
<4E661FAE.9020008@gmail.com>
Date: Tue, 6 Sep 2011 15:31:34 +0200
X-Google-Sender-Auth: PU01jajUbZuAxNk8IAoah8ohCk8
Message-ID: <CANEZrP3=UPYkBQo6b421xaMGyP4BsGiw8DBuM8pT2ow1Vom9JQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: shadders.del@gmail.com
Content-Type: multipart/alternative; boundary=bcaec51d2780a7728104ac45d899
X-Spam-Score: -0.8 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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
0.0 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service
-0.3 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1R0vkZ-0004Ly-Rp
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Building a node crawler to map network
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, 06 Sep 2011 13:31:40 -0000
--bcaec51d2780a7728104ac45d899
Content-Type: text/plain; charset=UTF-8
>
> I've looked but can't find a post like you're talking about. Can you point
> me to it?
>
https://groups.google.com/forum/?pli=1#!topic/bitcoinj/LSlZdUWcCdk
> If so then bollocks... I'm looking for something useful to do atm.
> PoolServerJ is in a holding pattern atm as I've stabilisied all the bugs I
> know about and am waiting for several pools to finish testing and move into
> production so I'm twiddling thumbs trying to figure out how to spend my
> time.
>
Patches to BitCoinJ are always welcome :-)
If you'd rather do your own thing, you could experiment with writing a proxy
that sits in front of bitcoind and multiplexes connections. Gavin is
concerned about socket exhaustion as users move to lightweight clients.
Multiplexing proxies are a battle-tested technique for reducing the strain
of this type of thing. BitCoinJ uses thread-per-connection so wouldn't do a
good job of that right now, but allowing it to use a mix of async io and
multi-threading would be a nice improvement. It'd need some changes to
bitcoind as well for a really good effort, to allow for IPs to be forwarded.
I'm happy to discuss it more with you over on the bitcoinj list if wanted.
--bcaec51d2780a7728104ac45d899
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class=3D"im=
">I've looked but can't find a post like you're talking about. =
=C2=A0Can you point me to it?<br>
</div></blockquote><div>=C2=A0</div><div><a href=3D"https://groups.google.c=
om/forum/?pli=3D1#!topic/bitcoinj/LSlZdUWcCdk">https://groups.google.com/fo=
rum/?pli=3D1#!topic/bitcoinj/LSlZdUWcCdk</a></div><div>=C2=A0</div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex;">
<div class=3D"im">If so then bollocks... I'm looking for something usef=
ul to do atm. =C2=A0PoolServerJ is in a holding pattern atm as I've sta=
bilisied all the bugs I know about and am waiting for several pools to fini=
sh testing and move into production so I'm twiddling thumbs trying to f=
igure out how to spend my time.</div>
</blockquote><div><br></div><div>Patches to BitCoinJ are always welcome :-)=
</div><div><br></div><div>If you'd rather do your own thing, you could =
experiment with writing a proxy that sits in front of bitcoind and multiple=
xes connections. Gavin is concerned about socket exhaustion as users move t=
o lightweight clients. Multiplexing proxies are a battle-tested technique f=
or reducing the strain of this type of thing. BitCoinJ uses thread-per-conn=
ection so wouldn't do a good job of that right now, but allowing it to =
use a mix of async io and multi-threading would be a nice improvement. It&#=
39;d need some changes to bitcoind as well for a really good effort, to all=
ow for IPs to be forwarded. I'm happy to discuss it more with you over =
on the bitcoinj list if wanted.</div>
</div>
--bcaec51d2780a7728104ac45d899--
|
