Javascript 处理连续的 JSON 流

Process a continuous stream of JSON

提问by Gabriele Cirulli

The (now defunct) page http://stream.twitter.com/1/statuses/sample.jsonused to return a continuous and endless stream of JSON data.

（现已不存在的）页面http://stream.twitter.com/1/statuses/sample.json用于返回连续和无休止的 JSON 数据流。

I'd like to process it using jQuery (or JavaScript, but preferably jQuery) inside my own web page to be able to display visual effects based on the live feed of tweets.

我想在我自己的网页中使用 jQuery（或 JavaScript，但最好是 jQuery）来处理它，以便能够根据推文的实时提要显示视觉效果。

Since as far as I know the jQuery parseJSONfunction will only execute the callback function after all the data has been sent by the server, but this is actually a continuous stream of data. How can I process the data "as it happens" but still keep the connection running?

因为据我所知 jQueryparseJSON函数只会在服务器发送完所有数据后才会执行回调函数，但这实际上是一个连续的数据流。我怎样才能“在发生时”处理数据但仍然保持连接运行？

回答by ErikE

This sort of thing is best done using WebSocketsnow, which according to CanIUse.Com is available in all major browsersexcept Opera Mini (see that link for more details about older or all browsers, and click the Resources tab to see even more links). As an overview, websockets are supported in IE 10+, Firefox 11+ (38+ if within a WebWorker context), Chrome 16+, Opera 12.1+, Safari 7+, Android 4.4+, Opera Mobile 12.1+.

这种事情现在最好使用WebSockets来完成，根据 CanIUse.Com 的说法，它在除 Opera Mini 之外的所有主要浏览器中都可用（有关旧浏览器或所有浏览器的更多详细信息，请参阅该链接，并单击“资源”选项卡以查看更多链接） . 作为概述，IE 10+、Firefox 11+（如果在 WebWorker 上下文中为 38+）、Chrome 16+、Opera 12.1+、Safari 7+、Android 4.4+、Opera Mobile 12.1+ 支持 websocket。

Note: you will likely want to learn about Service Workers and Web Workersas well, though those have different use cases and different abilities.

注意：您可能还想了解Service Workers 和 Web Workers，尽管它们有不同的用例和不同的能力。

It looks like this:

它看起来像这样：

var connection = new WebSocket(
   'ws://html5rocks.websocket.org/echo',
   ['soap', 'xmpp']
);

Attaching some event handlers immediately to the connection allows you to know when the connection is opened, when you've received incoming messages, or if an error has occurred.

将一些事件处理程序立即附加到连接可以让您知道连接何时打开、何时收到传入消息或是否发生错误。

Sending messages becomes as easy as this:

发送消息变得如此简单：

connection.send('your message');
connection.send(binaryData);

See Introducing WebSockets: Bringing Sockets to the Webfor a full explanation on how to do this.

有关如何执行此操作的完整说明，请参阅WebSockets 简介：将 Sockets 引入 Web。

ASP.Net developers: if for some reason you need to support older browsers and don't want to figure out for yourself how to deal with those that don't support WebSockets, consider using a library such as SignalR.

ASP.Net 开发人员：如果出于某种原因您需要支持较旧的浏览器并且不想自己弄清楚如何处理那些不支持 WebSockets 的浏览器，请考虑使用诸如SignalR 之类的库。

The Old EventSource API Answer For Older Browsers

旧版浏览器的旧 EventSource API 答案

Most browsers now implement the EventSource API, which makes long polling really easy, as long as the stream can be delivered with content-type text/event-stream. Older browsers or those developers who for any reason can't engineer the stream to have that content-type can use some helper scriptto do the same thing.

大多数浏览器现在都实现了EventSource API，这使得长轮询非常容易，只要流可以使用 content-type 传送text/event-stream。较旧的浏览器或那些出于任何原因无法设计流以具有该内容类型的开发人员可以使用一些帮助脚本来做同样的事情。

Here's an example:

下面是一个例子：

var jsonStream = new EventSource('https://example.com/yourstreamingservice')
jsonStream.onmessage = function (e) {
   var message = JSON.parse(e.data);
   // handle message
};

This is basically a full-fledged version of the exact thing that I outline below.

这基本上是我在下面概述的确切内容的完整版本。

The Even Older Service Streaming Answer For REALLY OLD Browsers

对于非常老的浏览器，更旧的服务流媒体答案

What you want is called long polling. You'll need a custom AJAX onreadystatechangehandling function. Instead of waiting until the entire stream has completed (since it never will), you'll need to examine the contents periodically. Note that you'll need to do some heavy lifting for this to work in IE 9 and lower, using an iframe.

你想要的是长轮询。您将需要一个自定义的 AJAXonreadystatechange处理函数。您无需等待整个流完成（因为它永远不会完成），而是需要定期检查内容。请注意，您需要做一些繁重的工作才能在 IE 9 及更低版本中使用iframe.

Roughly:

大致：

• Respond to each onreadystatechangeevent and examine the stream you've been given up to the current character to see if there is enough data to consume one or more discrete events. You'll need to parse the stream yourself with javascript string-handling functions. A combination of split, indexOf, regular expressions, looping, and so on can be used to accomplish this task.
• If there's not enough content yet, then exit and wait for the next event.
• I am pretty sure that each time the onreadystatechangehandler fires, the responseTextwill be all the data that has been received so far. Define a persistent variable that will hold the position of the first character that hasn't been properly processed yet.
• Once there is enough content for one or more discrete events to appear in the stream, take them out one at a time and pass them to your JSON parser to actually render the text as objects. Use them normally.

• 响应每个onreadystatechange事件并检查您已分配给当前角色的流，以查看是否有足够的数据来使用一个或多个离散事件。您需要使用 javascript 字符串处理函数自己解析流。可以使用 split、indexOf、正则表达式、循环等的组合来完成此任务。
• 如果还没有足够的内容，则退出并等待下一个事件。
• 我很确定每次onreadystatechange处理程序触发时，responseText都将是迄今为止收到的所有数据。定义一个持久变量，该变量将保存尚未正确处理的第一个字符的位置。
• 一旦有足够的内容让一个或多个离散事件出现在流中，一次将它们取出一个并将它们传递给您的 JSON 解析器以实际将文本呈现为对象。正常使用它们。

Check out this HTTP Streaming gistfor one resource, or Streaming as an alternative to polling the serverat SoftwareAs. If you must support IE 9 or older, then you'll need to use the iframemethod for that.

查看此HTTP Streaming gist以获取一种资源，或Streaming 作为在 SoftwareAs轮询服务器的替代方法。如果您必须支持 IE 9 或更早版本，则需要使用该iframe方法。

Here is a quote fromthe book Ajax Design Patterns: Creating Web 2.0 Sites with Programming and Usability Patterns:

以下引用自《Ajax 设计模式：使用编程和可用性模式创建 Web 2.0 站点》一书：

In summary, Service Streaming makes the HTTP Streaming approach more flexible, because you can stream arbitrary content rather than Javascript commands, and because you can control the connection's lifecycle. However, it combines two technologies that aren't consistent across browsers, with predictable portability issues. Experiments suggest that the Page Streaming technique does work on both IE [9 and older] and Firefox, but Service Streaming only works on Firefox, whether XMLHTTPRequest or IFrame is used. In the first case IE [9 and older] suppresses the response until its complete, with the IFrame it works if a workaround is used: The IE [9 and older] accepts a message from the server after the first 256 bytes so the only thing to do is to send 256 dummy Bytes before sending the messages. After this all messages will arrive as expected. So a full Service Streaming is possible in IE [9 and older], too!

总之，Service Streaming 使 HTTP Streaming 方法更加灵活，因为您可以流式传输任意内容而不是 Javascript 命令，并且因为您可以控制连接的生命周期。但是，它结合了两种跨浏览器不一致的技术，具有可预测的可移植性问题。实验表明，Page Streaming 技术在 IE [9 及更早版本] 和 Firefox 上都有效，但 Service Streaming 仅适用于 Firefox，无论是使用 XMLHTTPRequest 还是 IFrame。在第一种情况下，IE [9 及更早版本] 会抑制响应直到其完成，如果使用变通方法，则 IFrame 会起作用：IE [9 及更早版本] 在前 256 个字节之后接受来自服务器的消息，因此唯一的事情要做的是在发送消息之前发送 256 个虚拟字节。在此之后，所有消息都将按预期到达。

Mind you that it is from 2006, so it is definitely out of date, but if you have to support older browsers, it's still relevant.

请注意，它是从 2006 年开始的，所以它肯定是过时的，但是如果您必须支持旧浏览器，它仍然是相关的。

Security Issues

安全问题

Normal AJAX cannot go cross-domain, meaning (now that I pay attention to the fact that you want to stream from twitter) that you won't be able to do what you're asking. This can be worked around with JSONP, but JSONP by nature can't be service streamed and moreover isn't offered by twitter anyway. There is also Cross-Origin Resource Sharing(CORS) but twitter's not going to set that up for you--that's the kind of thing they'd only do for domains affiliated with them. And CORS requires a modern browser.

普通的 AJAX 不能跨域，这意味着（现在我注意到你想从 twitter 流式传输的事实）你将无法做你所要求的。这可以通过 JSONP 解决，但 JSONP 本质上不能进行服务流式传输，而且无论如何 twitter 也不提供。还有跨域资源共享(CORS)，但 twitter 不会为你设置——这是他们只为附属域做的事情。而且 CORS 需要现代浏览器。

Your only option is thus to create a proxy service on your web server that performs the requests to twitter for you and then hands out the data. This can only be done from the same domain as the main page was served from. Doing this would also allow you to create a version that will work for IE using the iframe technique. If you don't care about old IE versions, you can implement CORS yourself to defeat the domain restriction, if you know the domain that will be making the requests.

因此，您唯一的选择是在您的 Web 服务器上创建一个代理服务，为您执行对 twitter 的请求，然后分发数据。这只能从与提供主页的同一域中完成。这样做还允许您使用 iframe 技术创建一个适用于 IE 的版本。如果您不关心旧的 IE 版本，如果您知道将发出请求的域，您可以自己实现 CORS 来克服域限制。

If you have full control of the client software (like if this is for a corporate intranet) there is another option: hosting the web browser inside of a compiled locally-executed application's user form. I have only done this using C# but I imagine it's possible from other languages. When you use the right browser object, because it's hosted inside a C# application, the C# application can defeat the cross-domain security restrictions, reading and writing all page content no matter what domain it comes from. I doubt your situation is this one but I wanted to put the option here for others who might appreciate it.

如果您可以完全控制客户端软件（就像这是用于企业内部网），还有另一种选择：将 Web 浏览器托管在已编译的本地执行应用程序的用户表单中。我只使用 C# 做到了这一点，但我想其他语言也可以做到这一点。当您使用正确的浏览器对象时，因为它托管在 C# 应用程序中，C# 应用程序可以克服跨域安全限制，读取和写入所有页面内容，无论它来自哪个域。我怀疑你的情况是这样的，但我想把这个选项放在这里，供其他可能欣赏它的人使用。

回答by jimhigson

I've got an open source project which allows this on modern browsers (and falls back to a jQuery-style on older ones). The call syntax is similar to jQuery.ajax:

我有一个开源项目，它允许在现代浏览器上执行此操作（并在旧浏览器上回退到 jQuery 样式）。调用语法类似于 jQuery.ajax：

http://oboejs.com

http://oboejs.com

回答by Darin Dimitrov

The url you have specified in your question sends a JSON response stream. Due to cross domain security restrictions in browsers you cannot access it using javascript. You will need to implement a bridge server side script on your server which you could pollat regular intervals using AJAX requests or host your site on twitter.com. The first seems more feasible.

您在问题中指定的 url 发送 JSON 响应流。由于浏览器中的跨域安全限制，您无法使用 javascript 访问它。您需要在您的服务器上实现一个桥接服务器端脚本，您可以使用 AJAX 请求定期轮询或在twitter.com. 第一个似乎更可行。

回答by Kon

A web page at a very fundamental level can't keep a live/running connection to a server. Web browser sends a request to the server. Server sends a response (the HTML and more) back to the client (web browser). Think of this as a stateless model - no connection is ever kept alive after the request and response have been completed.

一个非常基础级别的网页无法保持与服务器的实时/运行连接。Web 浏览器向服务器发送请求。服务器将响应（HTML 等）发送回客户端（Web 浏览器）。将此视为无状态模型 - 在请求和响应完成后，没有任何连接保持活动状态。

Therefore, you have to do it yourself. You have to invoke additional, periodic requests from the client-side.

因此，您必须自己做。您必须从客户端调用额外的、定期的请求。

One way would be to periodically call your AJAX/GET functionality via setInterval()function. For example:

一种方法是通过setInterval()函数定期调用您的 AJAX/GET功能。例如：

setInterval(function() {

    $.ajax({
      url: "mydata/get",
      success: function(){
        // update content.
      }
    });

}, 5000);

This will fire off an AJAX request to mydata/get (or whatever URL you want to use) every 5 seconds.

这将每 5 秒向 mydata/get（或您想使用的任何 URL）发出一次 AJAX 请求。