From: Jeff Garzik <jgarzik@bitpay•com>
To: Melvin Carvalho <melvincarvalho@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Core 0.10 release schedule
Date: Mon, 27 Oct 2014 07:37:47 -0400 [thread overview]
Message-ID: <CAJHLa0MMBdZZMfPrT11ABODGEzNwUzinbv0Q985VWkhEJpoung@mail.gmail.com> (raw)
In-Reply-To: <CAKaEYh+suOdfnJ=GN6v_Gp=yNh4n2Bp+juv89BgBwZ_Mo+GfjQ@mail.gmail.com>
On Mon, Oct 27, 2014 at 7:24 AM, Melvin Carvalho
<melvincarvalho@gmail•com> wrote:
> Do you think it would a reasonable idea to put down some thoughts and
> proposals in a BIP?
It would certainly be nice to start with a document that reflects the
new REST interface. That makes a good starting point for further
discussion.
In general the interface exports what information is already
available. As Wladimir notes, there is no plan to turn this into a
full fledged block explorer, if that implies adding indices etc.
Feedback on the HTTP headers and form, and additional thoughts &
proposals are welcome. My pull request is intended to present
something minimal, that is easy to review and merge. My own list of
further to-dos includes
* last-modified and etag headers
* export UTXOs a la Mike Hearn's getutxos query
* eventually rebuild the RPC server to something multithreaded a la
https://github.com/jgarzik/rpcsrv
PR #2844 @ https://github.com/bitcoin/bitcoin/pull/2844
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
prev parent reply other threads:[~2014-10-27 12:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 7:57 Wladimir
2014-10-26 8:53 ` Luke Dashjr
2014-10-27 7:31 ` Wladimir
2014-10-26 8:55 ` odinn
2014-10-26 9:10 ` Wladimir
2014-10-26 18:17 ` odinn
2014-10-26 11:44 ` Melvin Carvalho
2014-10-27 7:49 ` Wladimir
2014-10-27 11:24 ` Melvin Carvalho
2014-10-27 11:37 ` Jeff Garzik [this message]
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=CAJHLa0MMBdZZMfPrT11ABODGEzNwUzinbv0Q985VWkhEJpoung@mail.gmail.com \
--to=jgarzik@bitpay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=melvincarvalho@gmail$(echo .)com \
/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