The first thought is to make a Socket.io client, well it's not that hard except that you'll be busy hacking the Socket.io protocol which is not standard (WebSocket is a standard). I've done something like this in the past but it was a waste of time.
Since Node.Js has a shared scope (The Global Scope) and it's mostly a single process application, you can always make a dedicated HTTP server for non-realtime interacting with Socket.io:
var app = require('http').createServer(function S(req, res){
res.writeHead(200, {
'Content-Type': 'text/html'
});
res.end('');
var i;
var sockets = io.sockets.sockets;
for (i in sockets) {
if (sockets.hasOwnProperty(i)) {
var socket = sockets[i];
// you have res, and socket so so something with it!
socket.emit('myevent', {msg: "json is cool :)"});
}
}
});
var io = require('socket.io').listen(app);
app.listen(80);
io.sockets.on('connection', function (socket) {
socket.on('theirsevent', function (data) {
});
});
IMHO this is way better that modifying apache with even more modules. This could even work with Python and .Net since it's HTTP.
I think this is much simpler/cleaner that any other solution. ... Unless there is some use case that this solution does not fit.
