Skip to content

Conversation

slavchev
Copy link

This PR deprecates #365

@ns-bot
Copy link

ns-bot commented Mar 11, 2016

💚

@ns-bot
Copy link

ns-bot commented Apr 4, 2016

💔

@ns-bot
Copy link

ns-bot commented Apr 4, 2016

💚

@slavchev
Copy link
Author

slavchev commented Apr 4, 2016

ping @atanasovg @blagoev @Pip3r4o @Plamen5kov

@ns-bot
Copy link

ns-bot commented Apr 5, 2016

💚

@Plamen5kov
Copy link
Contributor

👍

@ns-bot
Copy link

ns-bot commented Apr 11, 2016

💚

@slavchev slavchev merged commit a0f5d11 into master Apr 12, 2016
@slavchev slavchev deleted the slavchev/bytebuffer-support branch April 19, 2016 13:30
@andy-maca
Copy link

andy-maca commented May 15, 2018

@slavchev Seems current only direct byte buffer is supported, how about heap buffere? I am using nativescript-websocket plugin which is using java-websocket, but unfortunately it returns java.nio.HeapByteArray for every received message, when I use ArrayBuffer.from(..), there will be error message 'Error: Direct ByteBuffer expected)', so how can I get rid of this without doing data copy? Thanks.

@slavchev
Copy link
Author

@andy-maca Currently I don't work on NativeScript Android Runtime, but I looked at the implementation and it should be easy to extend it. I used isDirect check for performance reasons, but this constraint can be relaxed. It's a trade-off between copying/non-copying operations and usability. You can continue the discussion with the team /cc @vtrifonov @darind @mbektchiev @etabakov

@andy-maca
Copy link

andy-maca commented May 17, 2018

@slavchev Thanks. I just created a new issue #1060

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

Successfully merging this pull request may close these issues.

4 participants