[WIP] Enable WebSockets via Swoole

[kingIZZZY]

[WIP] Laravel Octane Swoole WebSockets

Already using Laravel Octane via Swoole?

Take full advantage of Swoole built-in WebSockets features to serve Laravel powered WebSockets!

Configure octane.swoole.enableWebSockets to true to enable

[kingIZZZY]

To access the Swoole server object from laravel code - here is one way how:

app('Laravel\Octane\Swoole\WorkerState')->server

For example to push WebSocket messages to clients:

app('Laravel\Octane\Swoole\WorkerState')->server->push($clientSocketFD, $message);

Is this the 1) only way? 2) correct way? If anyone knows - please share 🙏

[kingIZZZY]

Pretty much copied from handleTick/handleTask, does it make sense? Should it be doing these same steps for incoming WebSocket messages/disconnect?

[taylorotwell]

Would need to be Echo compatible IMO.

[kingIZZZY]

Could we keep the PR open for a bit longer to 1) maybe hear some more opinions 2) maybe attract some more attention of others better well versed with Echo than myself who can take up contributing on that aspect?

Or is there an evident impossibility of compatibility with Echo which dooms this whole approach/effort that I am missing?

[goodevilgenius]

Personally, I think this looks like a really good start to me.

Only suggestion I have is that I don't think the union type for Server|WServer is necessary. Last time I checked, Swoole\WebSocket\Server extends Swoole\Http\Server. So, you can just type check the Http server and that covers both.

Making it work with echo would be the logical next step, though.

[kingIZZZY]

Oh no 😭 I think I might abandon this effort for now
It seems this feature is prone to throwing this exception possibly among others:

• BindingResolutionException: Target class [events] does not exist.

Because: Laravel does not support Swoole Coroutines

• Looking forward to support for Swoole coroutines #765 specifically this comment

Seems it might be a deal breaker for now, oh well - it's back to Hyperf for me...
Anyone who'd like can also check out the Laravel-Hyperf project (see the above linked issue #765 and specific comment)