Due to "https://en.bitcoin.it/wiki/Transaction_fees" there are two types of fees. Logic for the mandatory comission is not so clear. Also it's difficult to check via existing api will whether the mandatory fee be charged or not. So the command to check will whether the mandatory fee be charged or not will be useful.
Edit: clarified issue title
Seems, that your commit generally makes what I meant when creating this issue.
And yes - I meant RPC API. If you are able to enhance RPC - it will be amazing ) I do not use C++ much, creating new commit will be hard for me.
The rpc api could of cours be enhanced with that.
But now the sendtoaddress (and others) will normally response with a transaction-id.
I think we break compatibility if we would give other/more information back.
Any ideas?
It is not possible to to know in advance whether the 'mandatory fee' will be charged as this depends on the size of the transaction. The size of the transaction, in turn, depends on the output of the coin selection algorithm. This may have changed by the time the 'real' send happens (either due to non-determinism or concurrent threads).
It would be nice if the raw transactions API provided access to the coin selection and fee determination logic of the wallet. This would make it possible to first construct a transaction, and send it or not dependent on the fee. Right now using the raw transactions API means having to do coin selection yourself.
It would be nice if the raw transactions API provided access to the coin selection and fee determination logic of the wallet.
This has become possible with fundrawtransaction.