From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] getmemorypool BIP process
Date: Sat, 3 Mar 2012 10:44:15 -0500 [thread overview]
Message-ID: <201203031044.17005.luke@dashjr.org> (raw)
On Saturday, March 03, 2012 10:05:58 AM Gavin Andresen wrote:
> > HTTP and JSON-RPC are a client-server model; there is no way for the
> > server to make calls to the client. It's not practical to expect clients
> > to run their own JSON-RPC server - many cannot listen on WAN ports at
> > all.
>
> You're doing that thing where either you say something before you've
> done adequate research, or you're being needlessly pedantic; I just
> copied and pasted this from section 2.1 of the JSON-RPC spec:
I wasn't aware anyone was considering JSON-RPC over anything other than HTTP.
I've updated the draft to include long polling, and remove some assumptions of
using HTTP for transport.
next reply other threads:[~2012-03-03 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 15:44 Luke-Jr [this message]
2012-03-04 0:18 ` Stefan Thomas
-- strict thread matches above, loose matches on Subject: below --
2012-02-28 22:06 Luke-Jr
2012-03-03 14:23 ` Stefan Thomas
2012-03-03 15:00 ` Luke-Jr
2012-03-03 17:08 ` Michael Grønager
2012-03-04 0:18 ` Stefan Thomas
2012-03-03 23:51 ` Geir Harald Hansen
2012-03-04 1:04 ` Luke-Jr
2012-03-04 17:49 ` Geir Harald Hansen
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=201203031044.17005.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.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