Question

几个月前（2011年8月）我成功创建了一个node.js websockets服务器，该服务器使用基本的HTTP用户/密码身份验证连接到Twitter的Streaming API。为此，我聘请了Andre Goncalves的twitter-nodejs-websocket图书馆。

自创建此工作实施以来，Twitter已通过基本HTTP身份验证取消了对流API的访问，转而支持 OAuth 。在这个转变之后，我使用了Ciaran Jessup的node-oauth库，它成功地让我再次访问Streaming API（当我运行服务器时，我通过console.log成功输出推文（推文） - 见下文）

现在的问题是我的websockets服务器不再工作了。当我从命令行运行我的服务器并从浏览器点击客户端网页时，会立即触发websocket“onclose”事件。

我已经尝试了一切我能想到的工作。任何帮助将非常感谢！

server.js

var sys    = require('sys'),
    http   = require('http'),
    ws     = require("./vendor/ws"),
    base64 = require('./vendor/base64'),
    arrays = require('./vendor/arrays')

var OAuth = require('./oauth/oauth').OAuth;

var consumer_key        = '[...]'; //removed for obvious security reasons...
var consumer_secret     = '[...]';
var access_token        = '[...]';
var access_token_secret = '[...]';

oa = new OAuth("https://twitter.com/oauth/request_token",
                "https://twitter.com/oauth/access_token", 
                consumer_key,
                consumer_secret,
                "1.0A",
                null,
                "HMAC-SHA1");

var request = oa.get("https://stream.twitter.com/1/statuses/filter.json?track=google", access_token, access_token_secret );

// Response Parsing -------------------------------------------- //

var clients = [];
var message = "";

request.addListener('response', function (response) {

    response.setEncoding('utf8');

    response.addListener("data", function (chunk) {

        message += chunk;

        var newlineIndex = message.indexOf('\r');
        // response should not be sent until message includes '\r'.
        // Look at the section titled "Parsing Responses" in Twitter's documentation.
        if (newlineIndex !== -1) {
            var tweet = message.slice(0, newlineIndex);

            clients.forEach(function(client){
                // Send response to all connected clients
                client.write(tweet);
            });

            // this just tests if we are receiving tweets -- we are: terminal successfully outputs stream //
            var pt = JSON.parse(tweet);
            console.log('tweet: ' + pt.text);
        }
        message = message.slice(newlineIndex + 1);
    });

});
request.end();

// Websocket TCP server

ws.createServer(function(websocket){
  clients.push(websocket);
  websocket.addListener("connect", function(resource){
    // emitted after handshake
    sys.debug("connect: " + resource);
  }).addListener("close", function(){
    // emitted when server or client closes connection
    clients.remove(websocket);
    sys.debug("close");
  });
}).listen(8081);


// This basic http server works, so we know this port is open.
//
// var http = require('http');
// http.createServer(function (req, res) {
//   res.writeHead(200, {'Content-Type': 'text/plain'});
//   res.end('Hello World\n');
// }).listen(8081);

客户代码

<script type="text/javascript" charset="utf-8">
    ws = new WebSocket("ws://ec2-67-202-6-10.compute-1.amazonaws.com:8081");
    ws.onmessage = function(evt) {
        console.log('tweet')
    };
    ws.onclose = function() {
        console.log("socket closed");
    };
    ws.onopen = function() {
        console.log("connected...");
    };
</script>

Answer 1

也许您更新了浏览器？ websocket规范正在迅速发展。无论如何，我建议使用socket.io，因为如果浏览器过时或者websockets再次不兼容或者一个糟糕的代理阻止了websockets工作，它甚至还可以使用回退。

Answer 2

从twitter流中查看此示例事件流（它使用服务器发送的事件）：

https://github.com/chovy/nodejs-stream

如何使用Node.js和Websockets创建Twitter流？

2 个答案: