Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <shadders.del@gmail.com>) id 1R1brr-00026x-8h for bitcoin-development@lists.sourceforge.net; Thu, 08 Sep 2011 10:29:59 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.83.52 as permitted sender) client-ip=74.125.83.52; envelope-from=shadders.del@gmail.com; helo=mail-gw0-f52.google.com; Received: from mail-gw0-f52.google.com ([74.125.83.52]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1R1brq-0003s7-9X for bitcoin-development@lists.sourceforge.net; Thu, 08 Sep 2011 10:29:59 +0000 Received: by mail-gw0-f52.google.com with SMTP id 15so782495gwj.11 for <bitcoin-development@lists.sourceforge.net>; Thu, 08 Sep 2011 03:29:58 -0700 (PDT) Received: by 10.101.175.2 with SMTP id c2mr69053anp.103.1315477798026; Thu, 08 Sep 2011 03:29:58 -0700 (PDT) Received: from [10.1.1.50] (155.88-67-202.dynamic.dsl.syd.iprimus.net.au [202.67.88.155]) by mx.google.com with ESMTPS id 11sm333673ant.0.2011.09.08.03.29.55 (version=SSLv3 cipher=OTHER); Thu, 08 Sep 2011 03:29:56 -0700 (PDT) Message-ID: <4E68991E.2030806@gmail.com> Date: Thu, 08 Sep 2011 20:29:50 +1000 From: Steve <shadders.del@gmail.com> User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Thunderbird/3.1.13 MIME-Version: 1.0 To: Mike Hearn <mike@plan99.net> References: <4E6879B6.7090203@gmail.com> <CANEZrP1UV+7aG0hQbwV1ikfE0i_y6Pu3GnnbQd5756tNNpM29Q@mail.gmail.com> In-Reply-To: <CANEZrP1UV+7aG0hQbwV1ikfE0i_y6Pu3GnnbQd5756tNNpM29Q@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -1.4 (-) 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 (shadders.del[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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 0.2 AWL AWL: From: address is in the auto white-list X-Headers-End: 1R1brq-0003s7-9X Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] bitcoind multiplexing proxy - request/response routing problem X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: shadders.del@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, 08 Sep 2011 10:29:59 -0000 > 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. > Fair enough I'll take it to the bitcoinj list. I wanted to post here in case I got any nibbles from c developers about option 2. If anyone want's the follow this discussion on the other list it's here: https://groups.google.com/forum/#!topic/bitcoinj/kqiBq9VxL-k