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

RFC - Fallback for synchronous applications #91

Open
Deltachaos opened this issue Feb 19, 2021 · 1 comment
Open

RFC - Fallback for synchronous applications #91

Deltachaos opened this issue Feb 19, 2021 · 1 comment

Comments

@Deltachaos
Copy link

To continue discussion of #58

I am happy that feature #85 was merged. I am asking myself if we could make the integration of Drift into existing Symfony applications even more simple.

I am asking myself if the changes to the Kernel could be put into a Trait and we could create an AsyncKernelInterface that drift can check against do see if the Kernel supports Async operations.

We would need to make it possible to allow the application to implement async operations on the one hand, which are only enabled if they are running in a Drift context, and fallback to synchronous if they are executed using PHP-FPM.

Using this approach we may could also achieve that existing applications like Sulu, eZ Publish or OroCRM adopt "Drift" as an additional experimental application mode which would extend the popularity and adoption of the project.

@mmoreram
Copy link
Member

Completely agree.

Let me check what are you exactly proposing in order to allow a better adoption for external projects.
As soon as the server became a completely decoupled Drift project, makes sense to work in this direction.

Thanks for your thoughts!

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

2 participants