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 ) 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 ; 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: References: Date: Tue, 24 Jun 2014 12:12:27 +0200 X-Google-Sender-Auth: AaNsLwh24lED35xxDHiEu6jy4a4 Message-ID: From: Mike Hearn To: Wladimir 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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
From my experience the main thing people are mis= sing 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.

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.

The other good reason to have JSON-RPC support would be= to reuse the Core regression tests.=C2=A0

Anyway,= this is off topic :)
--047d7b41cc74630c7c04fc9232fd--