PHP long connection use case analysis

This time I will bring you a case analysis of PHP long connection usage. What are the precautions when using PHP long connection? The following is a practical case, let’s take a look.

Long Polling Technology

Hold a connection on the server side and do not return immediately until there is data. Return, this is the principle of long connection technology

The key to long connection technology is to hold an HTTP request and not respond to the request until there is new data, and then the client automatically initiates a long connection request again.

How to hold a request? The server-side code may look like this

set_time_limit(0); //这句很重要, 不至于运行超时
while (true) {
  if (hasNewMessage()) {
    echo json_encode(getNewMessage());
    break;
  }
  usleep(100000);   //避免太过频繁的查询
}

Yes, it is to hold a request through a loop so as not to return immediately. The request will be responded to after new data is queried. Then the client processes the data , initiate a long connection request again.

The client code is like this

<script>
  (function longPolling() {
    $.ajax({
      &#39;url&#39;: &#39;server.php&#39;,
      &#39;data&#39;: data,
      &#39;dataType&#39;: &#39;json&#39;,
      &#39;success&#39;: function(data) {
        processData(data);
        longPolling();
      },
      &#39;error&#39;: function(data) {
        longPolling();
      }
    });
  })();
</script>

A simple chat room

Through long connections, we can develop a simple web chat room

Next, we develop a simple web chat room through redis

1. When each client initiates a long connection, on the server The client generates a message queue corresponding to the user. Then it monitors whether there is new data, returns the data to the client for processing, and initiates a long connection request again.

2. When each client initiates a message, Broadcast the message queue.

The following is a code snippet:

<?php namespace church\LongPolling;
use Closure;
use church\LongPolling\Queue\RedisQueue;
use Symfony\Component\HttpFoundation\Request;
use Symfony\Component\HttpFoundation\JsonResponse;
class Server
{
  public $event = [];
  public $redisQueue = null;
  public $request = null;
  public $response = null;
  public function construct()
  {
    $this->redisQueue = new RedisQueue();
    $this->request = Request::createFromGlobals();
    $this->response = new JsonResponse();
  }
  public function on($event, Closure $closure)
  {
    if (is_callable($closure)) {
      $this->event[$event][] = $closure;
    }
  }
  public function fire($event)
  {
    if (isset($this->event[$event])) {
      foreach ($this->event[$event] as $callback) {
        call_user_func($callback, $this);
      }
    }
  }
  public function sendMessage($data)
  {
    switch ($data['type']) {
      case 'unicast':   //单播
        $this->unicast($data['target'], $data['data'], $data['resource']);
        break;
      case 'multicast':    //组播
        foreach ($data['target'] as $target) {
          $this->unicast($target, $data['data'], $data['resource']);
        }
        break;
      case 'broadcast':    //广播
        foreach ($this->redisQueue->setQueueName('connections') as $target) {
          $this->unicast($target, $data['data'], $data['resource']);
        }
        break;
    }
    $this->fire('message');
  }
  public function unicast($target, $message, $resource = 'system')
  {
    $redis_queue = new RedisQueue();
    $redis_queue->setQueueName($target)->push($resource . ':' . $message);
  }
  public function getMessage($target)
  {
    return $this->redisQueue->setQueueName($target)->pop();
  }
  public function hasMessage($target)
  {
    return count($this->redisQueue->setQueueName($target));
  }
  public function run()
  {
    $data = $this->request->request;
    while (true) {
      if ($data->get('action') == 'getMessage') {
        if ($this->hasMessage($data->get('target'))) {
          $this->response->setData([
            'state' => 'ok',
            'message' => '获取成功',
            'data' => $this->getMessage($data->get('target'))
          ]);
          $this->response->send();
          break;
        }
      } elseif ($data->get('action') == 'connect') {
        $exist = false;
        foreach ($this->redisQueue->setQueueName('connections') as $connection) {
          if ($connection == $data->get('data')) {
            $exist = true;
          }
        }
        if (! $exist) {
          $this->redisQueue->setQueueName('connections')->push($data->get('data'));
        }
        $this->fire('connect');
        break;
      }
      usleep(100000);
    }
  }
}

Long connections avoid too frequent polling. However, maintaining a long connection on the server also consumes additional resources. Performance during large concurrency Not ideal. You can consider using

in small applications. It is also recommended that the client uses the websocket protocol of html5 and the server uses swoole.

I believe you have already read the case in this article After mastering the method, please pay attention to other related articles on the php Chinese website for more exciting content!

Recommended reading:

Detailed explanation of the use of php namespace

##How to convert Chinese characters and pinyin with PHP Chinese tool class ChineseUtil

The above is the detailed content of PHP long connection use case analysis. For more information, please follow other related articles on the PHP Chinese website!