From: Steve <shadders.del@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] bitcoind multiplexing proxy - request/response routing problem
Date: Thu, 08 Sep 2011 18:15:50 +1000 [thread overview]
Message-ID: <4E6879B6.7090203@gmail.com> (raw)
4a/ Serialize all request/response exchanges. i.e. request comes in
from remote node, proxy aquires lock on the proxy-localdaemon channel
and sends request. Channel remains locked until response is received or
timeout (in which case remote node gets no response). Unlock channel
after response received and send to client.
Possibly messages that don't expect a response (e.g. relaying a tx
broadcast from remote node) can be pushed down a locked channel to
improve performance as they won't interfere with sequencing. Locked
channels may also receive other unsolicited messages from local daemon
before the expected response message which would be dealt with the same
as if they came from an unlocked channel.
Disadvantages: Idle time for channel while waiting for response. As
per option 2 this allows the proxy to stay dumb/thin but loses
opportunity for de-duplicating/caching unless option 1 is layered on top.
4b/ As per 4a but use all 125 available bitcoind connections in a
channel pool. Acquiring a lock on a channel consists of checking for an
unlocked channel first then waiting in a queue for one to become available.
next reply other threads:[~2011-09-08 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 8:15 Steve [this message]
2011-09-08 9:29 ` [Bitcoin-development] bitcoind multiplexing proxy - request/response routing problem Mike Hearn
2011-09-08 10:29 ` Steve
-- 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=4E6879B6.7090203@gmail.com \
--to=shadders.del@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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