Websocket 应用程序不是游戏、聊天、Twitter 客户端或市场指数
我搜索了 websocket 应用程序，我发现的唯一内容是游戏、Twitter 客户端、聊天和市场指数。我想知道是否有人知道任何使用上述应用程序中未提及的 websocket 的应用程序。
I've searched for websocket applications and the only things that I've found is games, twitter clients, chats and market indices. I want to know if anyone knows any applications that use websockets that are not mentioned in the above applications.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（7）
您可能对 noVNC 感兴趣，它是一个完整的 VNC 客户端（使用 Canvas 和 WebSocket）。
我两年前创建了 noVNC（VNC 客户端）（托管版本位于 http://noVNC.com），并且已经被其他几个著名项目和公司采用。
noVNC 使用 WebSockets 连接到 VNC 服务器。如果 VNC 服务器直接支持 WebSocket 连接（目前仅 libvncserver/x11vnc），则可以直接连接。否则，您需要使用 websockify 从 WebSocket 桥接到 TCP。 Websockify 并不特定于 RFB/VNC 协议，可用于创建可与任何现有网络服务通信的 Web 应用程序（我在 websockify 项目中拥有一个最小但可运行的 IRC 客户端和 telnet 客户端）。
You might be interested in noVNC which is a full VNC client (using Canvas and WebSocket).
I created noVNC (VNC client) two years years ago (hosted version at http://noVNC.com) and it has been adopted by several other notable projects and companies.
noVNC uses WebSockets to connect to the VNC server. If the VNC server supports WebSocket connections directly (currently only libvncserver/x11vnc) then you can connect directly. Otherwise, you need to use websockify to bridge from WebSockets to TCP. Websockify is not specific to the RFB/VNC protocol and can be used to create web applications that can communicate with any existing network service (I have a minimal but working start of an IRC client and telnet client in the websockify project).
任何使用实时协作的 Web 应用程序，例如协作编码或编辑文档。 （例如，MS Office 使用 SocketIO）
您还可以使用它随时向用户界面推送通知。对于新闻页面很有用。
Any web application that uses real time collaboration, like collaborative coding or editing documents. (E.g. MS Office uses SocketIO)
You can also use it to have push notifications to a user interface at any time. Can be useful for news pages.
以下是一些涉及 WebSocket 和 Arduino 的演示：
http://www.youtube.com/watch?v= va7j86thW5M
http://www.youtube.com/watch?v=aVJV2z-lQJE
http://yopero-tech.blogspot.com/2012/02/arduino-websocket.html
这里是通过 Android 控制器板控制的 Beatbox HTML5 音频播放器：
http://www.youtube.com/watch? v=NZvH8BH_3H4
免责声明：我是 Autobahn 的作者。
Here are some demos involving WebSockets and Arduino:
http://www.youtube.com/watch?v=va7j86thW5M
http://www.youtube.com/watch?v=aVJV2z-lQJE
http://yopero-tech.blogspot.com/2012/02/arduino-websocket.html
And here is a beatbox HTML5 audio player controlled from Android controller pad:
http://www.youtube.com/watch?v=NZvH8BH_3H4
Disclaimer: I am author of Autobahn.
trello.com 是一个使用 websockets 的网站。 这里是一篇关于所使用技术的精彩帖子
trello.com is a website that uses websockets. Here is a fantastic post on the tecnologies that are used
Kaazing 有一些在线演示（披露：我为 Kaazing 工作）：
Kaazing has a handful of demos online (disclosure: I work for Kaazing):
在这个问题提出一年后，似乎需要一个更普遍的回应。 WebSocket 还处于早期阶段，还没有大量应用程序。目前，主流浏览器都支持 websocket，但后端支持仍然很少。除了上面提到的 kaazing 之外，我还透露我已经编写了现有的符合标准的“服务器”之一。 （Websocket 服务器演示）
您可以将您现在所做的替换为http 与 websockets，但每个人都小心不要说这是需要完成的事情。 WebSockets 是一种双向通信机制；这意味着，如果您愿意，您可以将其用于所有用途，包括 http 类型的请求-响应。但你不需要替换http。如果你想要的是请求-响应，那么http就没有问题。这就是它的建造目的。 WebSockets 通过“升级”http 连接请求来发起。如果您仍然以目前为止主要完成的方式来考虑 Web 浏览器应用程序，那么您可能会同意 http ...该协议定义了大多数当前 Web 应用程序的特征（因为它就在那里） ）。
以前您可以在应用程序组件中进行双向通信，但在浏览器中却很困难……这就是粘性位所在。相信我，我已经编写了足够多的解决方法来了解……Applet 上的 Applet，等等。即使对于以前可能实现的标准，有一个适当的标准也很好。这意味着即使应用程序组件也将具有对开放双向通信的新标准化支持（在单个服务器的范围之外，等等......）。现在 WebSocket 已经出现，开发人员需要开始以不同的方式思考浏览器......更多的是一个通用界面......一个真正的应用程序界面，而不仅仅是猫图片和网上商店的界面。这应该带来的重大革命是不再需要下载和安装程序组件来使双向通信成为可能。
我在 Applet 时代开发的应用程序之一是自主或半自主机器人的控制站。使用浏览器（每个人在所有不同的设备上都有一个），它请求 Websocket。您的机器人外出做某事，需要联系或向人类操作员报告。操作员不必单击刷新即可获取消息，应用程序开发人员也不需要任何花哨的解决方法或构建自己的界面来立即将消息发送到浏览器。机器人的所有者/操作员不需要在手机或其他设备上安装软件应用程序。只需使用网络套接字。
过去的另一个例子是股票交易，当时人们编写了复杂的解决方法来完成它。现在可以更轻松地编写股票交易应用程序，以使用所有类型设备上的每个人的浏览器作为界面，而无需下载和安装股票交易应用程序。随着价格和其他信息的变化，浏览器也会更新。同时，交易者可以随时点击买入或卖出按钮等。
A year after the question was asked, it seems begging for a more general response. It's still early days for WebSockets without a lot of applications yet. At this point, major browsers support websockets but there is still little backend support. Besides kaazing, mentioned above, I disclose that I've written one of the existing standard conformant "servers." (Websocket Server Demonstration)
You can replace what you now do with http with websockets, but everyone is being careful not to say that it's something that needs to be done. WebSockets are a mechanism for bidirectional communication; which means, you can, if you want to, use it for everything, including http type request-response. But you don't need to replace http. If what you want is request-response, then there's nothing wrong with http. That's what it was built for. WebSockets are initiated by "upgrading" an http connection request. If you're still thinking about web-browser applications the way they've mostly been done to this point, then you're probably ok with http ... the protocol that's defined the character of most current web apps (because it was there).
You could previously get bidirectional communication in application components, but it was tough in the browser ... that's where the sticky bit was. Believe me, I've written enough work-arounds to know .. Applets upon Applets, etc. It's also good to have a standard in place, even for what was previously possible. This means that even app components will have a new standardized support for open bidirectional communication (outside the scope of a single server, etc. ...). Now that WebSockets are here, developers need to start thinking of the browser differently ... as more of a universal interface ... a real application interface, not just an interface for cat pictures and web shops. The big revolution this should bring is in no longer needing to download and install program components to make bidirectional communication possible.
One of the applications I worked on back in my Applet days, was a control station for autonomous or semi-autonomous robotics. Using the browser (everyone's got one on all those different devices), it was begging for websockets. Your robot is out doing something and needs to contact or report to the human operator. The operator doesn't have to click to refresh to get the message and the app developer doesn't need any fancy work-arounds or build their own interface to get the message to the browser immediately. The robot's owner / operator doesn't need to install a software app on the cell phone or whatever. Just use websockets.
Another example from the olden days, when people wrote complicated work-arounds to get it done, is stock trading. A stock trading application can now more easily be written to use everybody's browser on all types of devices as the interface, without the need to download and install a stock trading application. As prices and other information changes, the browser gets an update. At the same time, the trader can click a buy or sell button at any time, etc.
您当前正在执行的任何轮询操作。聊天是显而易见的。评论线程类似。曾经在 SO 上写过并回答过，并让它告诉您刚刚发布了另一个答案吗？可以用socket来完成。任何可以实时监控的内容，例如股票价格、网站流量、优步出租车的位置。我认为有很多机会。
Anything that you're currently doing with polling. Chat is the obvious one. Comment threads are similar. Ever write and answer on SO and have it tell you another answer was just posted? Can be done with a socket. Anything with realtime monitoring like stock prices, web site traffic, location of your Uber cab. I think there's a ton of opportunities available.