Author

Topic: different return codes when sending coins from CLI? (Read 8385 times)

sr. member
Activity: 350
Merit: 250
probiwon.com
Ummm, the command-line RPC is implemented on top of the JSON-RPC mechanism.

So if the command-line RPC is working on your machine, then the JSON-RPC is, too.


On my project bitcoin client runs as special 'bitcoin' user's program.
All communications between www-data (webserver user) and bitcoin client works through wrappers. User www-data don't knows JSON-RPC password.
legendary
Activity: 1652
Merit: 1186
Chief Scientist
Ummm, the command-line RPC is implemented on top of the JSON-RPC mechanism.

So if the command-line RPC is working on your machine, then the JSON-RPC is, too.
sr. member
Activity: 308
Merit: 252
Aren't the JSON-RPC commands the same as the command line, just ported over the http ? Both would return the same problem I believe.
sr. member
Activity: 350
Merit: 250
probiwon.com
You should be using Python or Perl or something when writing a high level interface. The CLI code is really just there to let you play with the server. You should try the python-jsonrpc library.

Not agree with you.

JSON-RPC provides too many permissions. For webshop you need only address generation and info about receiving coins to address. JSON-RPC will provide an opportunity after site hack steal coins through it with website's uid.

That is, you still need a wrapper that implenets only the necessary functions and that changes the uid (by sudo or suid)
full member
Activity: 210
Merit: 100
You should be using Python or Perl or something when writing a high level interface. The CLI code is really just there to let you play with the server. You should try the python-jsonrpc library.
sr. member
Activity: 350
Merit: 250
probiwon.com
Please make a different return codes for bitcoin client when sending coins from command line.

Now amount error and address error have equal return codes and becomes difficult to distinguish error while writing a high-level interface.

Jump to: