Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.170 as permitted sender)
	client-ip=74.125.82.170; envelope-from=runesvend@gmail.com;
	helo=mail-we0-f170.google.com; 
MIME-Version: 1.0
In-Reply-To: <51EEDB57.4070108@monetize.io>
References: <CAJHLa0Ou1xF=LeLVu_wH1-XgJ1PavDV7_NHoDevo3R9+4z-ZfQ@mail.gmail.com>
	<201307231030.14139.andyparkins@gmail.com>
	<20130723094703.GA25900@savin>
	<ksllu7$9i$1@ger.gmane.org> <51EEDB57.4070108@monetize.io>
From: =?ISO-8859-1?Q?Rune_Kj=E6r_Svendsen?= <runesvend@gmail.com>
Date: Sat, 10 Aug 2013 22:30:46 +0200
Message-ID: <CAH2=CKz2epe2rJFPDN5FdqNK8X58CCMaHLVHPgK23tNmq6cRwg@mail.gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11c25aa0531bc404e39dc5a8
Subject: Re: [Bitcoin-development] HTTP REST API for bitcoind
Precedence: list

--001a11c25aa0531bc404e39dc5a8
Content-Type: text/plain; charset=ISO-8859-1

I think this is a useful feature, but I din't see why it should be a part
of bitcoind. I've created a simple HTTP REST wrapper around bitcoind's RPC
interface in Python:
https://github.com/runeksvendsen/btchttp/blob/master/btchttp.py

It simply runs a HTTP server that translates HTTP GET requests into the
relevant RPC request, and responds to the GET request with the relevant
data.

/Rune

On Tue, Jul 23, 2013 at 9:36 PM, Mark Friedenbach <mark@monetize.io> wrote:

>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> On 7/23/13 3:29 AM, Andreas Schildbach wrote:
> >
> > Yes, I understand that. For this reason, I would vote for adding the
> > usual HTTP authentication/SSL stuff to the REST API. That way, SPV users
> > can decide to run their own instance of the API (providing the needed
> > resources themselves).
> >
> > Or, a trusted party can set up a server. For example, I would be willing
> > to set it up for users of Bitcoin Wallet. I don't expect shitloads of
> > paper wallets sweeps for the forseeable future.
> >
> >
> Anyone who wants HTTP authentication or TLS can wrap it with nginx, or
> something similar. In the process they could put appropriate
> restrictions in place on incoming requests, and the onus would be on
> them, not us to keep it secure.
>
> Mark
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBAgAGBQJR7ttWAAoJEAdzVfsmodw4UmIP/36lK2TDc7mLTT8rbflJhl3v
> TL4CFKhXj6OuzG7tyino3Djs4EQnyk+CbpfOmJ8kYr29GPaZttuDJhYXtJqQBQCi
> DPq79ktudHnVMLPirEs7dUrLo+TAqhYX+8Sj+eTlW+p6YZg3JbkOAIPJG7597OK4
> zzU8Oxr0XKJFfGscKfkPThxJboNqzJYGl3otHUMXM4HsbIRYmrx4QSr8y7dsVgTd
> YZnD4bJO+eY4ZPzCcFdkPD/8bXQyKC5nPOH8/79lARNLESwB4OW79uf9q86EuH2O
> jZQ1qwpRNHblrNWS1/U2E4+7hEidvgZBwQhj+HbWgKiPWh4Df1lEXq6bLQQwdn6/
> b+jfiwg7xpb7eB2M4gPZ0uF/1TIcGJN3+LWEULFNTT/vsjyD/UU63ahZ1kVv7X0m
> W1NrbKjXxDbip+x3N7HLIu3zqAAaa0ele7OysyFCL6ZlwwafwJiEZZgHn2Iw7I1L
> S7lYBbFoLfXlOMVXNaKHPEV5gQEveMROJVBtnWkqShPQM0N/+Z+TXZes37up0GVo
> d7ptPfNbUNDTFc8Jj3+5rIyy3dUvSyMJlHZhsLmtCUnbQ867ZOgeUS52a8XQ+nJY
> 8IsShLfLk6fRWmHrwo9lzZQ/TbbUNyoUje0Ns6iL7G3IZwDqJH3kAGb/bkj/piDu
> tPNcN8bkYeNobTFIH+o4
> =jV80
> -----END PGP SIGNATURE-----
>
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

--001a11c25aa0531bc404e39dc5a8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think this is a useful feature, but I din&#39;t see why =
it should be a part of bitcoind. I&#39;ve created a simple HTTP REST wrappe=
r around bitcoind&#39;s RPC interface in Python:=A0<a href=3D"https://githu=
b.com/runeksvendsen/btchttp/blob/master/btchttp.py" target=3D"_blank">https=
://github.com/runeksvendsen/btchttp/blob/master/btchttp.py</a><div>


<br></div><div>It simply runs a HTTP server that translates HTTP GET reques=
ts into the relevant RPC request, and responds to the GET request with the =
relevant data.</div><div class=3D"gmail_extra"><br clear=3D"all"><div>
<div>/Rune</div></div><div><br></div><div class=3D"gmail_quote">On Tue, Jul=
 23, 2013 at 9:36 PM, Mark Friedenbach <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:mark@monetize.io" target=3D"_blank">mark@monetize.io</a>&gt;</span> wro=
te:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<div><br>
<br>
On 7/23/13 3:29 AM, Andreas Schildbach wrote:<br>
&gt;<br>
&gt; Yes, I understand that. For this reason, I would vote for adding the<b=
r>
&gt; usual HTTP authentication/SSL stuff to the REST API. That way, SPV use=
rs<br>
&gt; can decide to run their own instance of the API (providing the needed<=
br>
&gt; resources themselves).<br>
&gt;<br>
&gt; Or, a trusted party can set up a server. For example, I would be willi=
ng<br>
&gt; to set it up for users of Bitcoin Wallet. I don&#39;t expect shitloads=
 of<br>
&gt; paper wallets sweeps for the forseeable future.<br>
&gt;<br>
&gt;<br>
</div>Anyone who wants HTTP authentication or TLS can wrap it with nginx, o=
r<br>
something similar. In the process they could put appropriate<br>
restrictions in place on incoming requests, and the onus would be on<br>
them, not us to keep it secure.<br>
<br>
Mark<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)<br>
Comment: GPGTools - <a href=3D"http://gpgtools.org" target=3D"_blank">http:=
//gpgtools.org</a><br>
Comment: Using GnuPG with Thunderbird - <a href=3D"http://www.enigmail.net/=
" target=3D"_blank">http://www.enigmail.net/</a><br>
<br>
iQIcBAEBAgAGBQJR7ttWAAoJEAdzVfsmodw4UmIP/36lK2TDc7mLTT8rbflJhl3v<br>
TL4CFKhXj6OuzG7tyino3Djs4EQnyk+CbpfOmJ8kYr29GPaZttuDJhYXtJqQBQCi<br>
DPq79ktudHnVMLPirEs7dUrLo+TAqhYX+8Sj+eTlW+p6YZg3JbkOAIPJG7597OK4<br>
zzU8Oxr0XKJFfGscKfkPThxJboNqzJYGl3otHUMXM4HsbIRYmrx4QSr8y7dsVgTd<br>
YZnD4bJO+eY4ZPzCcFdkPD/8bXQyKC5nPOH8/79lARNLESwB4OW79uf9q86EuH2O<br>
jZQ1qwpRNHblrNWS1/U2E4+7hEidvgZBwQhj+HbWgKiPWh4Df1lEXq6bLQQwdn6/<br>
b+jfiwg7xpb7eB2M4gPZ0uF/1TIcGJN3+LWEULFNTT/vsjyD/UU63ahZ1kVv7X0m<br>
W1NrbKjXxDbip+x3N7HLIu3zqAAaa0ele7OysyFCL6ZlwwafwJiEZZgHn2Iw7I1L<br>
S7lYBbFoLfXlOMVXNaKHPEV5gQEveMROJVBtnWkqShPQM0N/+Z+TXZes37up0GVo<br>
d7ptPfNbUNDTFc8Jj3+5rIyy3dUvSyMJlHZhsLmtCUnbQ867ZOgeUS52a8XQ+nJY<br>
8IsShLfLk6fRWmHrwo9lzZQ/TbbUNyoUje0Ns6iL7G3IZwDqJH3kAGb/bkj/piDu<br>
tPNcN8bkYeNobTFIH+o4<br>
=3DjV80<br>
-----END PGP SIGNATURE-----<br>
<div><div><br>
<br>
---------------------------------------------------------------------------=
---<br>
See everything from the browser to the database with AppDynamics<br>
Get end-to-end visibility with application monitoring from AppDynamics<br>
Isolate bottlenecks and diagnose root cause in seconds.<br>
Start your free trial of AppDynamics Pro today!<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D48808831&amp;iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D48808831&amp;iu=3D/4140/ostg.clktrk</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div></div>

--001a11c25aa0531bc404e39dc5a8--