Binary messages? about mock-socket HOT 6 OPEN

It seems to work as long as you consistently use ArrayBuffer and related views on both sides.

If you send a Buffer type from Node something seems to get crossed and an empty ArrayBuffer appears on the other side.

server.on('connection', socket => {
  socket.on('message', (msg) => {
    const encodedAsNodeBuffer = myBufferGenerator();
    const newBuffer = new ArrayBuffer(encodedAsNodeBuffer.byteLength);
    const newBufferView = new Uint8Array(newBuffer);
    newBufferView.set(encodedAsNodeBuffer, 0);
    socket.send(newBuffer);
  }
}

The protobufjs code generator seems to use Buffer on the Node side, so something to be aware of if you are using that.

from mock-socket.

@dtracers right now there is no native support for binary messages but it will be on of the next things I work on adding.

from mock-socket.

+1

from mock-socket.

@cades or @dtracers do you have any examples I could use as a test case? If so I will be able to add support quickly

from mock-socket.

I use protobuf.js.

So a good example test might be sending a hello world protobuf file via
binary.

I don't think I'll be able to come up with one until this weekend. And
maybe not even then.
On Jun 5, 2015 11:01 AM, "Travis Hoover" [email protected] wrote:

@cades https://github.com/cades or @dtracers
https://github.com/dtracers do you have any examples I could use as a
test case? If so I will be able to add support quickly

—
Reply to this email directly or view it on GitHub
#6 (comment).

from mock-socket.

I don't know if something changed in the meantime, but this works:

    var binaryDataBuffer = new ArrayBuffer(1),
        binaryDataArray = new Uint8Array(binaryDataBuffer);

    clientInstance.onmessage = function(event) {
        var data = new Uint8Array(event.data);
        QUnit.equal( data[0], 1, "didn't receive the right data" );
    };

    binaryDataArray[0] = 1;
    serverInstance.send(binaryDataBuffer);

from mock-socket.