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 ) 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 ; 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> <4E661FAE.9020008@gmail.com> Date: Tue, 6 Sep 2011 15:31:34 +0200 X-Google-Sender-Auth: PU01jajUbZuAxNk8IAoah8ohCk8 Message-ID: From: Mike Hearn 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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
I've looked but can't find a post like you're talking about. = =C2=A0Can you point me to it?
=C2=A0
=C2=A0
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.

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 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.
--bcaec51d2780a7728104ac45d899--