Aleksei Gagarin
Aleksei Gagarin
I agree with you and i hope to see the task (in the internal task manager) of completely redesigning DB in the foreseeable future. Related: - https://github.com/spiral/database/issues/56
> spiral/database#56 is different It is different but related. I think without connection pool we won't be able to support properly a non-blocking database drivers
At the same time it is necessary to block the using connection or provide another connection if a second query must be executed in parallel with the first.
> What version it would target, if implemented? We haven't planned it yet
I've been using Injector in production with php-di for almost a year now. Works great.
The both links look broken
Looks like a breaking change. WDYT @butschster ? Should it be configurable?
We use `TEMPORAL_ADDRESS` env in our `temporal-bridge` https://github.com/spiral/temporal-bridge/blob/38be446ffe9feae7ba26fe5d22876b7786fe08f7/src/Bootloader/TemporalBridgeBootloader.php#L124
New methods might be: ```php // Return WorkflowStubInterface $wfClient->newWorkflow($class, ...); $wfClient->newRunningWorkflow($class, ...); // Return Proxy objects. There is `Proxy` suffix $wfClient->newWorkflowProxy($class, ...); $wfClient->newRunningWorkflowProxy($class, ...); // Untyped (unknown class name). Return...