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

PHP: Go async with AMP #451

Open
lennartdohmann opened this issue May 7, 2024 · 2 comments
Open

PHP: Go async with AMP #451

lennartdohmann opened this issue May 7, 2024 · 2 comments

Comments

@lennartdohmann
Copy link
Contributor

Use AMPHP to go async

@lennartdohmann lennartdohmann linked a pull request May 7, 2024 that will close this issue
@lennartdohmann lennartdohmann removed a link to a pull request May 7, 2024
@lennartdohmann lennartdohmann linked a pull request May 7, 2024 that will close this issue
@unglaublicherdude
Copy link
Member

I tested the implementation on an IONOS webhosting (shared-hosting) server and it does run there. 👍

@unglaublicherdude
Copy link
Member

We ran into an issue with async php by using the revolt/eventloop (dependency of the amphp packgages).

The nextcloud-app fails (only in the ci) when updating the http-client to the amphp one.

There is an issue with the revolt/eventloop and opcache which we can workaround by deactivate the opcache for the vendor/amphp directory. But for now, we decided to don't put anymore effort into this.

I opened this revoltphp/event-loop#95.
I opened this amphp/http-client#365.

With this issue, this PR is also basically obsolete too.

What we still have to do is to revert the http-client to the guzzle one or to build a factory that creates an http-client regarding to some ini-settings (opcache.enabled would lead to good old guzzle).

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