Added sendBinary method for WebSocket class.

[kyubuns]

I want to send binary on websocket!

[kyubuns]

With implementation as you say,(WebSocket.send(ubyte[] data) and WebSocket.send(String data))
the function send not text but binary in past code like below.

WebSocket.send(cast(ubyte[])"foo");

Is it alright?

[s-ludwig]

I hope that just now, the number of people using the old send() is countable with one hand and I would like to take that chance to still be able to make such a change without causing too much harm. But do you know the exact difference between the two on the JavaScript side? Is binary data received as a BinData object instead of a string?

[kyubuns]

I know, but websocket spec contains opcode.
hard-coding of opcode value(FrameOpcode.Text) is ugly.
I will send pull request which is your implement(two overloads of send) later.

[s-ludwig]

I was just asking because I don't know how browsers handle binary messages. But I agree that the hard-coded value is wrong and this needs to be fixed.

[kyubuns]

for example:
var ws = new WebSocket("ws://localhost:9998");
ws.onmessage = function (e) {
console.debug(e.data.constructor); //print type of e.data
};

↓

opcode==Text

function String() { [native code] }

opcode==Binary

function Blob() { [native code] }
function ArrayBuffer() { [native code] } //ws.binaryType = 'arraybuffer';