From: Steve <shadders.del@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] bitcoind multiplexing proxy - request/response routing problem
Date: Thu, 08 Sep 2011 20:29:50 +1000 [thread overview]
Message-ID: <4E68991E.2030806@gmail.com> (raw)
In-Reply-To: <CANEZrP1UV+7aG0hQbwV1ikfE0i_y6Pu3GnnbQd5756tNNpM29Q@mail.gmail.com>
> 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
next prev parent reply other threads:[~2011-09-08 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 8:15 Steve
2011-09-08 9:29 ` Mike Hearn
2011-09-08 10:29 ` Steve [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-08 2:11 Steve diy-eco-life
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=4E68991E.2030806@gmail.com \
--to=shadders.del@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/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