Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Binary support #8

Closed
ps2 opened this issue Jul 26, 2011 · 4 comments
Closed

Binary support #8

ps2 opened this issue Jul 26, 2011 · 4 comments

Comments

@ps2
Copy link

ps2 commented Jul 26, 2011

The onSuccess callback passes a String. Are there any plans to support binary responses? I have modifications to your source that would return a byte[], but that changes the api.

@loopj
Copy link
Collaborator

loopj commented Aug 4, 2011

I'm planning on supporting byte[] responses and streamed data responses on a future release. If you've already done this for byte[] responses it would be great to see a diff or a pull request! It should be ok to change the api since we can have multiple onSuccess handlers for different types.

@ronny
Copy link

ronny commented Oct 5, 2011

I've added support for byte array responses on my fork. The approach might not be the best (suggestions welcome), but it works for what we needed. In any case, just putting it here for future reference for other folks that are looking for a workaround.

playup@c7f3a2f

@ngocdaothanh
Copy link

Is this issue fixed?

@Dr1Ku
Copy link

Dr1Ku commented Aug 17, 2012

Yes, I believe this issue is fixed, there is a BinaryHttpResponseHandler one can use, declare your (extra) accepted Content-Types and use the on*(byte[] binaryData) @OVERRIDES.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants