Simple secure websocket (wss) chat using Node.js server and Jquery client

This article shows a static file server built in Node.js without using any frameworks. The current state of Node.js is such that almost everything we need for the static file server is provided by built-in APIs and a few lines of code.

最近在学习HTML5相关的东西，看到WebSocket是个很强大的技术，于是乎就小试了一下，做了个简单的聊天室。 WebSocket的原理就不多介绍了，如果想自己实现WebSocket服务器的话具体协议看这里：猛击   （不知道各位看官能不能看下去，反正我是没有看！） 一、运行环境     1、服务

In this guide we'll walk through the implementation of a WebSocket-based ping application. In this application, the client sends a "ping" message to the server every second, and the server responds with a "pong" message. The client listens for "pong" messages and logs them, keeping track of how many message exchanges there have been.

WebSocket是HTML5开始提供的一种在单个 TCP 连接上进行全双工通讯的协议。 在WebSocket API中，浏览器和服务器只需要做一个握手的动作，然后，浏览器和服务器之间就形成了一条快速通道。两者之间就直接可以数据互相传送。 浏览器通过 JavaScript 向服务器发出建立 We

Now that you know the purpose and potential benefits of server-side programming, we're going to examine in detail what happens when a server receives a "dynamic request" from a browser. As most website server-side code handles requests and responses in similar ways, this will help you understand what you need to do when writing most of your own code.

对于聊天室，大家应该都不陌生，笔者也写过很多关于聊天室的例子。 本节，我们将演示如何通过Node.js来实现一个WebSocket聊天服务器的例子。 ## 使用ws创建WebSokcet服务器 Node.js原生API并未提供WebSocket的支持，因此，需要安装第三方包才能使用WebSocket

Node.js is a cross-platform JavaScript runtime environment that allows developers to build server-side and network applications with JavaScript.

上节中带大家基于websoket与nodejs搭建了一个基本的聊天室雏形，实现了基本的聊天消息首发，用户状态显示，异常处理。但是这里仍然有个问题，我们发现聊天消息看不出来是谁发送的，并且与用户状态提示消息混杂在一起，很不友好，需要优化。 本节将实现用户消息的发送人显示，将聊天消息与用户状态提示消息用

The WebSocketStream API is a Promise-based alternative to WebSocket for creating and using client-side WebSocket connections. WebSocketStream uses the Streams API to handle receiving and sending messages, meaning that socket connections can take advantage of stream backpressure automatically (no additional action required by the developer), regulating the speed of reading or writing to avoid bottlenecks in the application.