sfcod /
socketio
| Conditions | 8 |
| Paths | 2 |
| Total Lines | 57 |
| Code Lines | 30 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 0 | ||
Small methods make your code easier to understand, in particular if combined with a good name. Besides, if your method is small, finding a good name is usually much easier.
For example, if you find yourself adding comments to a method's body, this is usually a good sign to extract the commented part to a new method, and use the comment as a starting point when coming up with a good name for this new method.
Commonly applied refactorings include:
If many parameters/temporary variables are present:
| 1 | <?php |
||
| 93 | public function predis(SymfonyStyle $io) |
||
| 94 | { |
||
| 95 | $pubSubLoop = function () use ($io) { |
||
| 96 | /** @var \Predis\Client $client */ |
||
| 97 | $client = $this->redisDriver->getClient(true); |
||
| 98 | |||
| 99 | // Initialize a new pubsub consumer. |
||
| 100 | $pubSub = $client->pubSubLoop(); |
||
| 101 | |||
| 102 | $channels = []; |
||
| 103 | foreach ($this->broadcast->channels() as $key => $channel) { |
||
| 104 | $channels[$key] = $channel . '.io'; |
||
| 105 | } |
||
| 106 | |||
| 107 | // Subscribe to your channels |
||
| 108 | $pubSub->subscribe(array_merge(['control_channel'], $channels)); |
||
| 109 | |||
| 110 | // Start processing the pubsup messages. Open a terminal and use redis-cli |
||
| 111 | // to push messages to the channels. Examples: |
||
| 112 | // ./redis-cli PUBLISH notifications "this is a test" |
||
| 113 | // ./redis-cli PUBLISH control_channel quit_loop |
||
| 114 | foreach ($pubSub as $message) { |
||
| 115 | switch ($message->kind) { |
||
| 116 | case 'subscribe': |
||
| 117 | $io->success("Subscribed to {$message->channel}"); |
||
| 118 | break; |
||
| 119 | case 'message': |
||
| 120 | if ('control_channel' == $message->channel) { |
||
| 121 | if ('quit_loop' == $message->payload) { |
||
| 122 | $io->success("Aborting pubsub loop...\n"); |
||
| 123 | $pubSub->unsubscribe(); |
||
| 124 | } else { |
||
| 125 | $io->success("Received an unrecognized command: {$message->payload}\n"); |
||
| 126 | } |
||
| 127 | } else { |
||
| 128 | $payload = json_decode($message->payload, true); |
||
| 129 | $data = $payload['data'] ?? []; |
||
| 130 | |||
| 131 | $this->broadcast->on($payload['name'], $data); |
||
| 132 | } |
||
| 133 | break; |
||
| 134 | } |
||
| 135 | } |
||
| 136 | |||
| 137 | // Always unset the pubsub consumer instance when you are done! The |
||
| 138 | // class destructor will take care of cleanups and prevent protocol |
||
| 139 | // desynchronizations between the client and the server. |
||
| 140 | unset($pubSub); |
||
| 141 | }; |
||
| 142 | |||
| 143 | // Auto recconnect on redis timeout |
||
| 144 | try { |
||
| 145 | $pubSubLoop(); |
||
| 146 | } catch (ConnectionException $e) { |
||
| 147 | $pubSubLoop(); |
||
| 148 | } |
||
| 149 | } |
||
| 150 | } |
||
| 151 |
Loading history...
Let’s assume that you have a directory layout like this:
. |-- OtherDir | |-- Bar.php | `-- Foo.php `-- SomeDir `-- Foo.phpand let’s assume the following content of
Bar.php:If both files
OtherDir/Foo.phpandSomeDir/Foo.phpare loaded in the same runtime, you will see a PHP error such as the following:PHP Fatal error: Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.phpHowever, as
OtherDir/Foo.phpdoes not necessarily have to be loaded and the error is only triggered if it is loaded beforeOtherDir/Bar.php, this problem might go unnoticed for a while. In order to prevent this error from surfacing, you must import the namespace with a different alias: