From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XiizR-0008Fr-5e for bitcoin-development@lists.sourceforge.net; Mon, 27 Oct 2014 12:01:37 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.223.174 as permitted sender) client-ip=209.85.223.174; envelope-from=jgarzik@bitpay.com; helo=mail-ie0-f174.google.com; Received: from mail-ie0-f174.google.com ([209.85.223.174]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XiizP-0005nM-FS for bitcoin-development@lists.sourceforge.net; Mon, 27 Oct 2014 12:01:37 +0000 Received: by mail-ie0-f174.google.com with SMTP id x19so4154156ier.19 for ; Mon, 27 Oct 2014 05:01:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=f8Y7WL55R9ZVVNhaJth5JrH5N57q2qrA9ablw07AZC8=; b=M7kdpFsRP828p8Mp8TBRFo75R2Tqul4Nf8gQecy3C7cazSierbuW5CdWyOGuw/z4mh M/YYoG2oSvo5CnfWJi79226YWFoVm7ohYdcQjk22n8Cb/+UqZnB77GJp7/guCNGCycRC VKz72Cg8QMy50XayeYq0n5WpnDQYBEnIvyVG6hP60cbfTRArSnopdmpVaqwkwOMGXQeY LGCr3GxXaxCqsjvgCBU5+6TDG0z4V4UT2UB7TFE19G46aIy3TI8S3JtrXkugyAk77zV8 wX1u6Ikmxv6uA1G6kUzGLSE5/KH6KUu1iy3lOaQcaoAVRD/E+s1IJqv5W4Y6rMA3++HI CsyQ== X-Gm-Message-State: ALoCoQlP2IgeRZj8wpWc8eZRCAOrsbNQLy5z5j6kNNhXHKxX4mFTSQANP2UuOm/Kt0Z1TOTGe29Z X-Received: by 10.107.128.106 with SMTP id b103mr8466392iod.42.1414409887277; Mon, 27 Oct 2014 04:38:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.156.193 with HTTP; Mon, 27 Oct 2014 04:37:47 -0700 (PDT) In-Reply-To: References: From: Jeff Garzik Date: Mon, 27 Oct 2014 07:37:47 -0400 Message-ID: To: Melvin Carvalho Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1XiizP-0005nM-FS Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Bitcoin Core 0.10 release schedule X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 12:01:37 -0000 On Mon, Oct 27, 2014 at 7:24 AM, Melvin Carvalho 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/