php websocket fallback to ajax best practices - php

Question

Everything is working perfectly with this set:
I'm using docker-compose running some containers: nginx:1.22.0-alpine, php:8.1-cli, php:8.1.10-fpm, redis:7.0.5, [...].
My folders within the server are like:
-var/www/web
-var/www/web/sharedPHPScript.php
-var/www/web/public
-var/www/web/public/index.php
-var/www/web/core/ajax
-var/www/web/core/ajax/ajax.parser.php
-var/www/web/core/websocket
-var/www/web/core/websocket/websocket.php
-var/www/web/core/websocket/websocket.parser.php
[...]
I just mounted the same host /var/www/web into both containers: php:8.1-cli, php:8.1.10-fpm.
This way I need just to code from my host and the code state are replicated in both containers.
I just picked php:8.1-cli to run my websocket-server because I was benchmarking for performance but I do not know if would be better to use php-fpm to it.
on docker-composer.yml:
version: '3.7'
services:
[...]
fpm:
[...]
volumes:
- ./web:/web:delegated
swoole:
[...]
volumes:
- ./web:/web:delegated
index.php includes a controller that manage to call ajax.php when ever I send a fetch request from the client:
index.php>controller.php>include('/web/sharedPHPScript.php')
websocket.php keeps running like a thread listening for connections to spaw filedescriptors to the server:
use Swoole\WebSocket\Server;
// Init redis
$redis = new Redis();
$redis->connect(REDIS['host'], REDIS['port']);
// Create websocket instance
$server = new Server("0.0.0.0", 8443);
[...]
// Register the "onOpen" event handler
$server->on("open", function (Server $server, $request) use(&$redis) {
[...]
include('/web/sharedPHPScript.php')
}
[...]
My client (using javascript) onload event, creates a websocket connection with the server: server-ip/websocket>nginx:1.22.0-alpine>php:8.1-cli.
If the websocket connection status is not working, it just start using an ajax fetch.
function sendJSON(obj){
// check if ws is active
console.log('socket.readyState',socket.readyState);
// use Websocket
if(socket.readyState === 1){
wsSend(obj); // some wrapper for socket.send();
return;
}
// use AJAX
ajaxSend(obj); // some wrapper for ajax fetch().then()
}
My doubt is:
As I want to use this /web/sharedPHPScript.php to handle the fetches comming from php-fpm and the socket comming from php-cli, for better debugging as no need to write for two diferent data flows and database connections, I'm creating some wrap functions to decide which action to take depending on the origin (from websocket.parser.php or ajax.parser.php). inside /web/sharedPHPScript.php:
if($continue){ sendGlobal($req,$server,$request); $continue = dieGlobal($req); }
if($continue){
sendGlobal($object,$server,$request);
$continue = dieGlobal($req);
}
if(!$continue){return;}
from vendor/autoload.php from each container:
composer.json:
[...]
"autoload":{
"psr-4":{
"Classes\\":"../web/core/!classes/"
}
}
/web/core/!classes/sharedFunctions.php:
// Requests
// used for ajax
function sendAJAX($obj){
header("Content-type: application/json");
echo json_encode($obj);
}
// used for ws
function sendWS($obj,$server,$request){
if($server && $request){$server->push($request->fd, json_encode($obj));}
}
// used for both ajax and ws (Global)
function sendGlobal($obj,$server=0,$request=0){
if(isset($obj->ajax)){ sendAJAX($obj); }
if(isset($obj->ws)){ sendWS($obj,$server,$request); }
}
function dieGlobal($obj){
if(isset($obj->ajax)){ die; }
if(isset($obj->ws)){ return false; }
}
from ajax.parser.php:
$ajax = true;
$req = (object)$_POST;
$continue = true;
$server=null;
$request=null;
include('/web/sharedPHPScript.php');
from websocket.parser.php:
$ws=true;
include('/web/sharedPHPScript.php');
The problem is that php-cli as running a loop, I cannot use php commands like die;,setheader();,echo(); to send the http response back to the client. And from php-fpm, I do not have a $server or $request object, etc... Not even mentioning the wrapper for the $_SESSION...
So I'm woundering if there is a better/cleaner/simpler (in terms of best practice) way to do this websocket fallback to ajax because it is working like a charm and performing very nice but the sharedPHPScript.php is looking ugly...
I tryed separated flows for each websocket and ajax connections but this way i realised, as the project grows, I would need to create two slightly different codes for each container to do the same task...