From: Mike Hearn <mike@plan99•net>
To: shadders.del@gmail•com
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Building a node crawler to map network
Date: Tue, 6 Sep 2011 15:31:34 +0200 [thread overview]
Message-ID: <CANEZrP3=UPYkBQo6b421xaMGyP4BsGiw8DBuM8pT2ow1Vom9JQ@mail.gmail.com> (raw)
In-Reply-To: <4E661FAE.9020008@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
>
> 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.
[-- Attachment #2: Type: text/html, Size: 1686 bytes --]
next prev parent reply other threads:[~2011-09-06 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 7:42 Steve
2011-09-06 8:29 ` Steve
2011-09-06 8:36 ` Christian Decker
2011-09-06 12:49 ` Mike Hearn
2011-09-06 13:27 ` Steve
2011-09-06 13:31 ` Mike Hearn [this message]
2011-09-06 14:17 ` Steve
2011-09-06 14:52 ` Mike Hearn
2011-09-06 15:25 ` Steve
2011-09-06 14:36 ` Rick Wesson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANEZrP3=UPYkBQo6b421xaMGyP4BsGiw8DBuM8pT2ow1Vom9JQ@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=shadders.del@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox