Implement api_send_transfer

[jkrvivian]

ta_send_transfer_res_serialize is removed because api_send_transfer returns the transaction object instead of transaction hash.

Close #8

[jserv]

Does operator != perform byte-by-byte character comparison?

[jkrvivian]

According to spec 21.4.8.3 operator !=
The above comparison fit this situation:

template<class charT, class traits, class Allocator>
   bool operator!=(const basic_string<charT,traits,Allocator>& lhs,
                            const charT* rhs);
Requires: rhs points to an array of at least traits::length(rhs) + 1elements of charT.
Returns: lhs.compare(rhs) != 0

And compare performs byte-by-byte character comparison, in [1] it uses the phrase lexicographical comparison([2]).

references:

• 1: char_traits::compare
• 2: lexicographical_compare

[wusyong]

Forgot to mention that after memory double free error has been fixed on dcurl. We should add pow_init() and pow_destroy() in ta_attach_to_tangle or somewhere else if you find it's more appropriate.

[jkrvivian]

@wusyong ,
Got it! I'll add it in ta_attach_to_tangle

[jserv]

Is there relevant test case available?

[jkrvivian]

Is there relevant test case available?

@jserv , We've tested here:

curl  localhost:8000/transaction -X POST -H "content-type:application/json" \
 -d \
'{"value":0,"tag":"TATATATATATATATATATATATATAT",\
"message":"TANGLEACCELERATORROCKS",\
"address":"9MIZW9SISDRQIVNVNBAPVWVMANZZFNXTGUDDISTYXKMFHLITTOSVFOUESIYINJLQLJAXVDRAI99NYFLPY"}'

The transaction can be found on tangle explorer!!
message: tangle accelerator rocks

[jserv]

The transaction can be found on tangle explorer!!
message: tangle accelerator rocks

cool. It takes 1 min to be confirmed.