MICROSOFT_PRESS_EBOOK_PROGRAMMING_WINDOWS_8_APPS_WITH_HTML_CSS_AND_JAVASCRIPT_PDF

FIGURE 14-7 Output of Scenario 2 of the Connecting with WebSockets sample (cropped).
Here’s the process in code, simplified from js/scenario2.js, where we see a similar pattern to what we
just saw for MessageWebSocket, only sending a continuous stream of data:
var streamWebSocket;
var dataWriter;
var dataReader;
var data = "Hello World";
var countOfDataSent;
var countOfDataReceived;
var webSocket = new Windows.Networking.Sockets.StreamWebSocket();
webSocket.onclosed = onClosed;
// The server URI is obtained and validated here, and stored in a variable named uri.
webSocket.connectAsync(uri).done(function () {
streamWebSocket = webSocket;
dataWriter = new Windows.Storage.Streams.DataWriter(webSocket.outputStream);
dataReader = new Windows.Storage.Streams.DataReader(webSocket.inputStream);
// When buffering, return as soon as any data is available.
dataReader.inputStreamOptions = Windows.Storage.Streams.InputStreamOptions.partial;
countOfDataSent = 0;
countOfDataReceived = 0;
// Continuously send data to the server
writeOutgoing();
// Continuously listen for a response
readIncoming();
}, function (error) {
var errorStatus = Windows.Networking.Sockets.WebSocketError.getStatus(error.number);
// [Output error message]
});
function writeOutgoing() {
686