• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            Error

            C++博客 首頁 新隨筆 聯系 聚合 管理
              217 Posts :: 61 Stories :: 32 Comments :: 0 Trackbacks

            WebSocket is an underlying network protocol that enables you to build other standard
            protocols on top of it.

            The WebSocket Protocol enables full duplex communication between a client and
            a remote server over the Web, and supports transmission of binary data and text strings.
            The protocol consists of an opening handshake followed by basic message framing, and is
            layered over TCP.


            WebSocket programming follows an asynchronous programming model, which
            means that as long as a WebSocket connection is open, your application simply listens
            for events. Your client does not need to actively poll the server for more information. To
            start listening for the events, you simply add callback functions to the WebSocket object.
            Alternatively, you can use the addEventListener() DOM method to add event listeners
            to your WebSocket objects.
            A WebSocket object dispatches four different events:
            · Open
            · Message
            · Error
            · Close
            As with all web APIs, you can listen for these events using on<eventname> handler
            properties, as well as using the addEventListener(); method.

            ws.onopen
            ws.onmessage
            ws.onerror
            ws.onclose

            e.data instanceof Blob
            ws.binaryType = "blob"

            WebSocket objects have two methods: send() and close()


            Listing 2-12. Waiting for the Open Event Before Sending a Message
            // Wait until the open event before calling send().
            var ws = new WebSocket("ws://echo.websocket.org")
            ws.onopen = function(e) {
            ws.send("Initial data");
            }

            Listing 2-13. Checking the readyState Property for an Open WebSocket
            // Handle outgoing data. Send on a WebSocket if that socket is open.
            function myEventHandler(data) {
            if (ws.readyState === WebSocket.OPEN) {
            // The socket is open, so it is ok to send the data.
            ws.send(data);
            } else {
            // Do something else in this case.
            //Possibly ignore the data or enqueue it.
            }
            }


            // Send a Blob
            var blob = new Blob("blob contents");
            ws.send(blob);
            // Send an ArrayBuffer
            var a = new Uint8Array([8,6,7,5,3,0,9]);
            ws.send(a.buffer);


            Listing 2-15. Calling the close() Method
            // Close the WebSocket connection
            ws.close();
            You can optionally pass two arguments to the close() method: code (a numerical
            status code) and reason (a text string). Passing these arguments transmits information
            to the server about why the client closed the connection. We will discuss the status
            codes and reasons in greater detail in Chapter 3, when we cover the WebSocket closing
            handshake. Listing 2-16 shows an example of calling the close() method with an
            argument.
            Listing 2-16. Calling the close() Method with a Reason
            // Close the WebSocket connection because the session has ended successfully
            ws.close(1000, "Closing normally");
            Listing 2-16 uses code 1000, which means, as it states in the code, that the
            connection is closing normally.


            WebSocket Object Attributes
            There are several WebSocket Object attributes you can use to provide more information
            about the WebSocket object: readyState, bufferedAmount, and protocol.

            Table 2-1. readyState Attributes, Values, and Status Descriptions
            Attribute Constant     Value     Status
            WebSocket.CONNECTING   0   The connection is in progress but has not been established.
            WebSocket.OPEN   1   The connection has been established. Messages can flow between the client and server.
            WebSocket.CLOSING   2   The connection is going through the closing handshake.
            WebSocket.CLOSED   3   The connection has been closed or could not be opened.

            WebSocket Object Attribute: protocol
            The protocol attribute is the empty string before the
            opening handshake completes and remains an empty string if the server does not choose
            one of the protocols offered by the client.

             

            posted on 2016-02-22 17:02 Enic 閱讀(273) 評論(0)  編輯 收藏 引用 所屬分類: websocket
            午夜人妻久久久久久久久| 奇米影视7777久久精品| 一本色道久久88加勒比—综合| 久久久久久无码Av成人影院| 久久96国产精品久久久| 久久青青国产| 国产亚洲精品自在久久| 久久久久国色AV免费观看| 久久久久久综合网天天| 少妇内射兰兰久久| 66精品综合久久久久久久| 中文字幕精品久久| 久久综合综合久久狠狠狠97色88| 久久精品国产99久久香蕉| 亚洲国产精品久久电影欧美 | 一本色综合久久| 精品久久人妻av中文字幕| 久久久久亚洲AV无码去区首| 2021精品国产综合久久| 久久午夜无码鲁丝片秋霞| 国产伊人久久| 99久久国产综合精品成人影院| 精品熟女少妇AV免费久久| 久久99精品久久久久久不卡| 狠狠色丁香久久综合五月| 99蜜桃臀久久久欧美精品网站| 久久精品国产精品亚洲下载| aaa级精品久久久国产片| 久久精品成人欧美大片| 日韩人妻无码一区二区三区久久99| 国内精品久久久久国产盗摄| 青青青国产精品国产精品久久久久| 精品久久久久久中文字幕人妻最新| 伊人久久综合精品无码AV专区| 久久人妻少妇嫩草AV蜜桃| 久久99精品久久久久久9蜜桃| 丰满少妇人妻久久久久久4| 久久99亚洲综合精品首页| 一本色道久久88加勒比—综合| 97久久综合精品久久久综合| 久久国产精品一区二区|