You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 10, 2024. It is now read-only.
Unfortunately, I couldn't find any other support option.
During peak times, I have the problem that connections sometimes take too long.
I could increase the port range in the kernel, but before doing that, I would like to address Swoole directly via TCP instead of routing it through port 1215, using unix:/tmp/mysocket.sock.
Swoole supports socket connections. How can I accomplish this?
Simply changing the host is not enough.
'host' => 'unix:/tmp/swoole.sock',
Here, "http://" is still being used.
I hope for a response.
Best regards,
Timo
The text was updated successfully, but these errors were encountered:
Hello,
Unfortunately, I couldn't find any other support option.
During peak times, I have the problem that connections sometimes take too long.
I could increase the port range in the kernel, but before doing that, I would like to address Swoole directly via TCP instead of routing it through port 1215, using unix:/tmp/mysocket.sock.
Swoole supports socket connections. How can I accomplish this?
Simply changing the host is not enough.
'host' => 'unix:/tmp/swoole.sock',
Here, "http://" is still being used.
I hope for a response.
Best regards,
Timo
The text was updated successfully, but these errors were encountered: