> 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 developer
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 no
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 respons
This a reworking of a post I made on the bitcoinj list under a
different topic but it's something I'd like to throw out there for
input.
I'm going to build a proof of concept this weekend of the multiplexing
proxy that Gavin and Mike were talking about here:
http://sourceforge.net/mailarchive/mess
4 matches
Mail list logo
