1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1WzNiM-0001VR-TC
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Jun 2014 10:12:34 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.182 as permitted sender)
client-ip=209.85.214.182; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f182.google.com;
Received: from mail-ob0-f182.google.com ([209.85.214.182])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WzNiL-0003JM-63
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Jun 2014 10:12:34 +0000
Received: by mail-ob0-f182.google.com with SMTP id nu7so63327obb.27
for <bitcoin-development@lists.sourceforge.net>;
Tue, 24 Jun 2014 03:12:27 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.132.203 with SMTP id ow11mr257711oeb.47.1403604747617;
Tue, 24 Jun 2014 03:12:27 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.35.234 with HTTP; Tue, 24 Jun 2014 03:12:27 -0700 (PDT)
In-Reply-To: <CA+s+GJDxLdKvtEE72B4biJ+1s3Yurm6ZHEaRi8H8nGMDo+vNiw@mail.gmail.com>
References: <CAC1+kJNjcPkaHiR8mzofwXE4+4UX5nmxX5Q3rZv37v-K40p1Tw@mail.gmail.com>
<CA+s+GJDVBQVu8yH9jLu_rQmk=dsJuMUctT-iK0zzOJRYgE8k9w@mail.gmail.com>
<CAC1+kJOQ2uBo2peYKZJyPSQL6qzk6Yu-cF-tPs3GzVS6cAc53w@mail.gmail.com>
<CANEZrP1bNs4ahMzd7AfSH3P39Cx1rkmCkjnOMOM9T2Anr5wVOw@mail.gmail.com>
<CA+s+GJDxLdKvtEE72B4biJ+1s3Yurm6ZHEaRi8H8nGMDo+vNiw@mail.gmail.com>
Date: Tue, 24 Jun 2014 12:12:27 +0200
X-Google-Sender-Auth: AaNsLwh24lED35xxDHiEu6jy4a4
Message-ID: <CANEZrP3hdJWhNN1qOge_Vcn1y_Xds_9cWB4g5aRDY3JLh8OVZg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Wladimir <laanwj@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b41cc74630c7c04fc9232fd
X-Spam-Score: -0.5 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1WzNiL-0003JM-63
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Plans to separate wallet from core
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2014 10:12:35 -0000
--047d7b41cc74630c7c04fc9232fd
Content-Type: text/plain; charset=UTF-8
>
> From my experience the main thing people are missing with BitcoinJ is
> a quick and easy way to set up a wallet as a daemon, to use the
> functionality from non-java through RPC.
Yes. I'd love to have a mostly Core compatible JSON-RPC frontend. Most of
my current users are happy using it as a library though. A lot of popular
languages can run directly on the JVM these days. The big ones we miss are
C++ and PHP, I think. But you can use JavaScript, Python 2.7, Lisp, Ruby,
along with other less well known ones.
The other good reason to have JSON-RPC support would be to reuse the Core
regression tests.
Anyway, this is off topic :)
--047d7b41cc74630c7c04fc9232fd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">From my experience the main thing people are mis=
sing with BitcoinJ is<br>
a quick and easy way to set up a wallet as a daemon, to use the<br>
functionality from non-java through RPC.</blockquote><div><br></div><div>Ye=
s. I'd love to have a mostly Core compatible JSON-RPC frontend. Most of=
my current users are happy using it as a library though. A lot of popular =
languages can run directly on the JVM these days. The big ones we miss are =
C++ and PHP, I think. But you can use JavaScript, Python 2.7, Lisp, Ruby, a=
long with other less well known ones.</div>
<div><br></div><div>The other good reason to have JSON-RPC support would be=
to reuse the Core regression tests.=C2=A0</div><div><br></div><div>Anyway,=
this is off topic :)</div></div></div></div>
--047d7b41cc74630c7c04fc9232fd--
|
