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.
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.