-
Notifications
You must be signed in to change notification settings - Fork 653
Add binary data transfer from .net extensions, as per XWALK-4615. #3963
Conversation
Testing patch series with zcr01/crosswalk@2967c50 as its head.
|
Thanks for the patch. You should probably rebase your patch to the current master (I can see a Merge branch 'master' of https://github.com/zcr01/crosswalk into HEAD") Also it's missing tests. |
Tests are here: crosswalk-project/crosswalk-test-suite#3847 |
Testing patch series with zcr01/crosswalk@f73c03a as its head.
|
It should be there : https://github.com/crosswalk-project/crosswalk/tree/master/extensions/test/win |
Ok - I'll put tests over there, probably tomorrow at this point. Sorry, first pr and the contribute page directed me to the other repository. |
Testing patch series with zcr01/crosswalk@1155c39 as its head.
|
Testing patch series with zcr01/crosswalk@f982fef as its head.
|
Testing patch series with zcr01/crosswalk@88b2d88 as its head.
|
Testing patch series with zcr01/crosswalk@9f04529 as its head.
|
Added tests and cleaned the history. |
Could you please just reformat the commit message to : [Windows] Add binary data transfer for .net extensions BUG=XWALK-4615 |
Exposes PostBinaryMessageToJS(byte[] data, ulong size) to the .net extension bridge. - Uses XW_MessagingInterface2 to return an ArrayBuffer to the Javascript client - Improves data transfer speed for large amounts of raw data, as translating from a string is slow in Javascript. BUG=XWALK-4615
Testing patch series with zcr01/crosswalk@697b2af as its head.
|
LGTM. I'll merge when the bots are green. Thanks for the patch. |
@darktears @zcr01: I think this broke our official Windows canary builds:
|
exports.binaryEcho = function(msg, callback) { | ||
binaryTestListener = callback; | ||
extension.postMessage(msg); | ||
}; |
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.
It's missing a " here.
Should be fixed now. I think I must have messed something up in the rebase and missed the commit where I fixed that. #3969 |
No description provided.