Standard network interface

In Cocos Creator, we support the most widely used standard network interface on the Web platform:

• XMLHttpRequest: for short connection
• WebSocket: for long connection

Of course, browsers on the Web platform support these two interfaces originally. The reason why we say Cocos Creator supports it is because when we release the native version, the user can operate it using these two network interface codes which follows the principle of "one set of code for multiple platforms operation" which Cocos honors.

How to use

1. XMLHttpRequest

   Simple example:

    var xhr = new XMLHttpRequest();
    xhr.onreadystatechange = function () {
        if (xhr.readyState == 4 && (xhr.status >= 200 && xhr.status < 400)) {
            var response = xhr.responseText;
            console.log(response);
        }
    };
    xhr.open("GET", url, true);
    xhr.send();
   

   Developers can use new XMLHttpRequest() directly or use cc.loader.getXMLHttpRequest() to create a connecting object. The effect of these two are the same.

   For the standard file of XMLHttpRequest, please refer to MDN Chinese file.

2. WebSocket

   Simple example:

    ws = new WebSocket("ws://echo.websocket.org");
    ws.onopen = function (event) {
        console.log("Send Text WS was opened.");
    };
    ws.onmessage = function (event) {
        console.log("response text msg: " + event.data);
    };
    ws.onerror = function (event) {
        console.log("Send Text fired an error");
    };
    ws.onclose = function (event) {
        console.log("WebSocket instance closed.");
    };
   
    setTimeout(function () {
        if (ws.readyState === WebSocket.OPEN) {
            ws.send("Hello WebSocket, I'm a text message.");
        }
        else {
            console.log("WebSocket instance wasn't ready...");
        }
    }, 3);
   

   For the standard file of WebSocket, please refer to MDN Chinese file.

SocketIO

Unfortunately, Creator does not provide Socket.io official support on the Web platform, requires users to add them themselves to the project. And the Socket.io of the native platform is discarded. Previously the socket.io for the native platform was implemented by a third-party developer and has not been maintained for a long time. So it is not recommended to use.

Beyond these, SocketIO provides packaging based on the WebSocket API which can be used on the Node.js server. If this library is needed, developers can reference SocketIO on their own.

Reference SocketIO in script:

1. Download SocketIO: https://socket.io
2. Drag the downloaded file into the route you would like to save in explorer

3. Modify SocketIO script to avoid the execution on native environment

   As web SocketIO can not parsed correctly in JSB, the Cocos provides native SocketIO on native environment. So we should hack to make the web SocketIO script not work on native environment, the way to achieve this is to modify the SocketIO script:

    if (!cc.sys.isNative) {
   
        // SocketIO original code
   
    }
   

4. Make the SocketIO script Import As Plugin, so we can access the SocketIO in the component by using window.io directly

5. To use SocketIO in the component you can go to SocketIO official website for API and files