-
Notifications
You must be signed in to change notification settings - Fork 16
Conversation
8115904
to
0cd2a1f
Compare
.post([&](served::response& res, const served::request& req) { | ||
char* json_result; | ||
|
||
if (req.header("content-type") != "application/json") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does operator !=
perform byte-by-byte character comparison?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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:
Forgot to mention that after memory double free error has been fixed on dcurl. We should add |
@wusyong , |
Is there relevant test case available? |
0cd2a1f
to
d33bf80
Compare
d33bf80
to
c3e4ad3
Compare
@jserv , We've tested here:
The transaction can be found on tangle explorer!! |
cool. It takes 1 min to be confirmed. |
ta_send_transfer_res_serialize
is removed becauseapi_send_transfer
returns the transaction object instead of transaction hash.Close #8