Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sock instead of webhost #557

Closed
TimoFrenzel opened this issue May 13, 2024 · 0 comments
Closed

sock instead of webhost #557

TimoFrenzel opened this issue May 13, 2024 · 0 comments

Comments

@TimoFrenzel
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant