Received-SPF: pass (sog-mx-2.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; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <4E6879B6.7090203@gmail.com>
References: <4E6879B6.7090203@gmail.com>
Date: Thu, 8 Sep 2011 11:29:25 +0200
Message-ID: <CANEZrP1UV+7aG0hQbwV1ikfE0i_y6Pu3GnnbQd5756tNNpM29Q@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: shadders.del@gmail.com
Content-Type: multipart/alternative; boundary=bcaec51d27805334d304ac6ab234
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] bitcoind multiplexing proxy -
 request/response routing problem
Precedence: list

--bcaec51d27805334d304ac6ab234
Content-Type: text/plain; charset=UTF-8

It's probably best to keep this discussion on just one mailing list. It's
confusing to have duplicate threads in different places. People will end up
making the same points.

To repeat what I posted elsewhere, for now I'd just start with the simplest
possible approach:

- Ignore version skew for now (disconnect older clients)

- Don't send received transactions/blocks to the bitcoind. Let it hear about
them from its own p2p connections. That way you will always receive all
valid transactions/blocks which you can then relay/cache/drop inbound
duplicates.

- Parse/handle inv/getblocks/getheaders requests so clients that connect and
catch up with the chain don't place any load on the bitcoind. If a client
requests data the proxy doesn't have in RAM, it can go fetch it from the
underlying bitcoind.

If you can make v1 work and demonstrate actual scalability improvements,
then you can always go back and make it smarter in v2.

--bcaec51d27805334d304ac6ab234
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

It&#39;s probably best to keep this discussion on just one mailing list. It=
&#39;s confusing to have duplicate threads in different places. People will=
 end up making the same points.<br><br><div>To repeat what I posted elsewhe=
re, for now I&#39;d just start with the simplest possible approach:</div>
<div><br></div><div>- Ignore version skew for now (disconnect older clients=
)</div><div><br></div><div>- Don&#39;t send received transactions/blocks to=
 the bitcoind. Let it hear about them from its own p2p connections. That wa=
y you will always receive all valid transactions/blocks which you can then =
relay/cache/drop inbound duplicates.</div>
<div><br></div><div>- Parse/handle inv/getblocks/getheaders requests so cli=
ents that connect and catch up with the chain don&#39;t place any load on t=
he bitcoind. If a client requests data the proxy doesn&#39;t have in RAM, i=
t can go fetch it from the underlying bitcoind.</div>
<div><br></div><div>If you can make v1 work and demonstrate actual scalabil=
ity improvements, then you can always go back and make it smarter in v2.</d=
iv>

--bcaec51d27805334d304ac6ab234--