remove toString

[nginnever]

I found that this was causing incorrect returns when writing the add http resource. JS-IPFS-API makes http requests to the js-ipfs object core now with the addition of the new add support for core here.

If the data is a string then the buffer is sent correctly, however if the data field is something else it seems to be wrapping the buffer with some extra maybe new line characters.

@diasdavid @dignifiedquire
Is there a specific reason for the data to be return as a string in the object/data http resource?

PR 323 Is blocked by this issue.

[hackergrrl]

Could you add a test case? I'm curious what data causes this to break.

[nginnever]

@noffle there is a test case of it failing here in the add http PR.

I'm looking into adding a direct test to object/data http-api test now.

The file otherconfig does not get the correct hash do to this issue. It's a plain text json doc while hello does get the correct data when toString() is applied. Could it be json plain text in a buffer being toString() that is the issue?

[dignifiedquire]

We should make sure that this is always the same type of object (which toString did).

[daviddias]

LGTM :)