Created
August 16, 2011 08:52
-
-
Save theturtle32/1148686 to your computer and use it in GitHub Desktop.
Example of how to fallback to alternative websocket library for old protocol clients.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/usr/bin/env node | |
var WebSocketRequest = require('websocket').request; | |
var http = require('http'); | |
var server = http.createServer(function(request, response) { | |
console.log((new Date()) + " Received request for " + request.url); | |
response.writeHead(404); | |
response.end(); | |
}); | |
server.listen(8080, function() { | |
console.log((new Date()) + " Server is listening on port 8080"); | |
}); | |
var serverConfig = { | |
// All options *except* 'httpServer' are required when bypassing | |
// WebSocketServer. | |
maxReceivedFrameSize: 0x10000, | |
maxReceivedMessageSize: 0x100000, | |
fragmentOutgoingMessages: true, | |
fragmentationThreshold: 0x4000, | |
keepalive: true, | |
keepaliveInterval: 20000, | |
assembleFragments: true, | |
// autoAcceptConnections is not applicable when bypassing WebSocketServer | |
// autoAcceptConnections: false, | |
disableNagleAlgorithm: true, | |
closeTimeout: 5000 | |
}; | |
// Handle the upgrade event ourselves instead of using WebSocketServer | |
server.on('upgrade', function(req, socket, head) { | |
var wsConnection; | |
var wsRequest = new WebSocketRequest(socket, req, serverConfig); | |
try { | |
wsRequest.readHandshake(); | |
wsConnection = wsRequest.accept(wsRequest.requestedProtocols[0], wsRequest.origin); | |
// wsConnection is now live and ready for use | |
} | |
catch(e) { | |
console.log("WebSocket Request unsupported by WebSocket-Node: " + e.toString()); | |
return; | |
// Attempt old websocket library connection here. | |
// wsConnection = /* some fallback code here */ | |
} | |
handleWebSocketConnect(wsConnection); | |
}); | |
function handleWebSocketConnect(connection) { | |
console.log((new Date()) + " Connection accepted."); | |
connection.on('message', function(message) { | |
if (message.type === 'utf8') { | |
console.log("Received Message: " + message.utf8Data); | |
connection.sendUTF(message.utf8Data); | |
} | |
else if (message.type === 'binary') { | |
console.log("Received Binary Message of " + message.binaryData.length + " bytes"); | |
connection.sendBytes(message.binaryData); | |
} | |
}); | |
connection.on('close', function(connection) { | |
console.log((new Date()) + " Peer " + connection.remoteAddress + " disconnected."); | |
}); | |
} |
I've updated the gist to reflect my update.
Here is a Gist that implements a working example of a server that handles draft-08/-09/-10 connections with WebSocket-Node and the rest with miksago's node-websocket-server:
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@nicokaiser -- As it turns out, you're quite right! Apologies! I've updated it the code in v0.0.16 not to automatically close the connection. That responsibility is deferred to WebSocketServer in the normal case, or you in the case where you're handling the fallback.