public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Wladimir <laanwj@gmail.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Plans to separate wallet from core
Date: Tue, 24 Jun 2014 12:12:27 +0200	[thread overview]
Message-ID: <CANEZrP3hdJWhNN1qOge_Vcn1y_Xds_9cWB4g5aRDY3JLh8OVZg@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJDxLdKvtEE72B4biJ+1s3Yurm6ZHEaRi8H8nGMDo+vNiw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 644 bytes --]

>
> 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 :)

[-- Attachment #2: Type: text/html, Size: 926 bytes --]

  reply	other threads:[~2014-06-24 10:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23  9:50 [Bitcoin-development] Plans to separate wallet from core Jorge Timón
2014-06-23 10:32 ` Wladimir
2014-06-23 20:15   ` Jorge Timón
2014-06-24  9:07     ` Wladimir
2014-06-24  9:44       ` Wladimir
2014-06-24 13:24         ` Thomas Voegtlin
2014-06-24 15:33       ` Justus Ranvier
2014-06-24 16:40         ` Jorge Timón
2014-06-25  5:43           ` Wladimir
2014-06-24  9:11     ` Mike Hearn
2014-06-24  9:40       ` Wladimir
2014-06-24 10:12         ` Mike Hearn [this message]
2014-06-24 11:29       ` Jorge Timón
2014-06-24 11:48         ` Tamas Blummer
2014-06-24 13:26           ` Jorge Timón
2014-06-24 13:37             ` Pieter Wuille
2014-06-24 11:58         ` Wladimir
2014-06-24 12:16           ` Mike Hearn
2014-06-24 12:41             ` Wladimir

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=CANEZrP3hdJWhNN1qOge_Vcn1y_Xds_9cWB4g5aRDY3JLh8OVZg@mail.gmail.com \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=laanwj@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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