The process of integrating phpsocketio with thinkphp5 was a pitfall that I personally stepped on!

Usage environment: thinkphp5.0

projectRequirements

The front-end places an order, and the back-end accepts it and prompts it immediately. For example: Meituan Takeaway, after the client successfully places an order, the merchant will immediately have a voice prompt for receiving the order.

Development environment

• thinkphp5.0
• phpsocketio

(Since the socket service needs to be started, It needs to be used in an environment that can satisfy the shell)

socketio Advantages

This is just my opinion. After all, I haven’t studied socketio in depth, so I just give a brief summary:

• Reduce server IO load
• Long connection ratioajaxPolling is reliable
• The service is stable and supports dynamic

After a brief look, the memory usage is very small, and there is only one process. According to official reports, one process can also accommodate high concurrency of 10,000 people, so it is more than enough for my project.

Official documentation

https://github.com/walkor/php...

Start development

Install phpsocketio

First cd to the project root directory of thinkphp. Use the following command

composer require workerman/phpsocket.io

(Composer will not explain here. If there is any problem, please ask me and it should be solved)

After installation, vendor There should be a workerman folder under the folder. If it exists, congratulations, it has been installed.

Service entry file

Go back to the project root directory and create a newsocketio.php, start editing

#!/usr/bin/env php
<?php define(&#39;APP_PATH&#39;, __DIR__ . &#39;/application/&#39;);
define(&#39;BIND_MODULE&#39;,&#39;socketio/Server/index&#39;);
// 加载框架引导文件
require __DIR__ . &#39;/thinkphp/start.php&#39;;

Just write it here and it will be OK. For all subsequent things, you can ignore his existence

Create service controller

In the socketio.php file in the previous step, module binding When we get to 'socketio/Server/index', we need to create it manually. In order to understand, I use the directory to display

├─application           应用目录
│  ├─socketio           新创建目录
│  │  ├─controller      
│  │  │  ├─Server.php   启动文件

Server.php

The entry file is only bound to this controller, so this is the core of the entire socketio.

<?php /*
 * (c) U.E Dream Development Studio
 *
 * Author: 李益达 - Ekey.Lee <ekey.lee@gmail.com>
 *
 * For the full copyright and license information, please view the LICENSE
 * file that was distributed with this source code.
 */
namespace app\socketio\controller;

require_once VENDOR_PATH . "workerman/phpsocket.io/src/autoload.php";

use PHPSocketIO\SocketIO;
use Workerman\Worker;

class Server
{

    public function index()
    {
        $io = new SocketIO(8080);//socket的端口
        $io->on('workerStart', function () use ($io) {
            $inner_http_worker = new Worker('http://0.0.0.0:5880');//这里IP不用改变，用的内网通讯，端口不能与socket端口想通
            $inner_http_worker->onMessage = function ($http_connection, $data) use ($io) {
                
                $io->emit('new_msg', '44444');//这里写了固定数据，请根据自己项目需求去做调整，不懂这里的可以看看官方文档，很清楚
                $http_connection->send('ok');
            };
            $inner_http_worker->listen();
        });

        // 当有客户端连接时
        $io->on('connection', function ($socket) use ($io) {
            // 定义chat message事件回调函数
            $socket->on('chat message', function ($msg) use ($io) {
                // 触发所有客户端定义的chat message from server事件
                $io->emit('chat message from server', $msg);
            });
        });

        Worker::runAll();
    }
}

Create API to trigger socketio

Similarly you can create a new API controller under socketio, this is only for testing

 public function api()
    {
        // 推送的url地址，使用自己的服务器地址
        $push_api_url = "http://0.0.0.0:5880";//这里同样不需要更改IP。只是端口一定需要和server.php onworker的一样
        $post_data = array(
           "type" => "publish",
           "content" => "这个是推送的测试数据",
        );
        $ch = curl_init ();
        curl_setopt ( $ch, CURLOPT_URL, $push_api_url );
        curl_setopt ( $ch, CURLOPT_POST, 1 );
        curl_setopt ( $ch, CURLOPT_HEADER, 0 );
        curl_setopt ( $ch, CURLOPT_RETURNTRANSFER, 1 );
        curl_setopt ( $ch, CURLOPT_POSTFIELDS, $post_data );
        curl_setopt ($ch, CURLOPT_HTTPHEADER, array("Expect:"));
        $return = curl_exec ( $ch );
        curl_close ( $ch );
        var_export($return);
    }

Now thereserverServer side, API trigger side, then it needs to be displayed, which is our front end

Front end

What I want to write now is the prompt received by the merchant. The previously written server server provides phpsocketio monitoring and socket services, and API provides event triggering, that is, the trigger after someone places an order. The order is used as an event to trigger the server socket, allowing him to Respond to the front-end

Please note before starting the code: the port and domain name here are roundabout

 <script></script>
  <script>
            // 连接服务端
            var socket = io(&#39;http://xxxx.com:8080&#39;);//这里请填写你的域名，外网，端口为socket端口
          // 后端推送来消息时
            socket.on(&#39;new_msg&#39;, function (msg) {//这里的new_msg请一定要注意，官方文档都写的是content，但是后端发送的自定义是new_msg，后端定义成new_msg，前端却接受content的字段。所以是接受不了的
                swal({ title: "包厢点餐提醒", text: "哆啦a梦包厢有新订单" })
                //console.log("收到消息：" + msg);
            });

</script>

There are two places where I had problems before

• Port Domain name: The domain name is the domain name of the external network. Of course, it needs to be under the same IP as your socket service, that is: your socket is deployed under the IP of 114.114.114.114. This domain name must be under the IP of 114.114.114.114. The port is the port of new SocketIO in the backend service.
• socket.on()The document contains socket.on('content',function(msg){....}), but you can read it In our Server.php $io->emit('new_msg', '');The custom event here is clearly called new_msg, but it is written as content , maybe I am blind and did not see it clearly, but I would also like to remind you that you must pay attention to the callback event name

After deployment, start running

Now that all files are deployed, enter server management and open shell. cdGo to the project root directory. Then execute

php socketio.php start

This time is only a work summary, because I was pressed for time and did not do a good job To study more about socketio, there may be some flaws, but I 100% guarantee that this was tested by me personally, and the pitfalls mentioned were all overcome by me step by step. If there is anything wrong, please let me know ^_^