Impl. response using PSR-7 interface

[abbadon1334]

App::outputXxx/terminateXxx methods not longer accepts $headers as 2nd param, call $app->setResponseHeader() before it if needed

[mvorisek]

request must be handled as PSR request as well

laminas dep should be not needed if this translates to a few echo/header/http_response_code lines

[abbadon1334]

request must be handled as PSR request as well

laminas dep should be not needed if this translates to a few echo/header/http_response_code lines

I replace with code, but because of the small difference in performance, I always prefer the ready-made solutions, which are already tested in almost every situation, even those we don't know at the moment.

[abbadon1334]

ui/src/App.php

Line 1119 in beb149f

exit(1);

Are you sure that this cannot be changed to an Exception or other ways to not force exit the process?
My fear is that if you use Atk4 in a routing/handler contest, that exit in place of an Error will stop the flow without an output, without running post route middleware or logging of the error, without considering that to avoid that line you must override via copy/paste the whole method just to remove it.

[abbadon1334]

request must be handled as PSR request as well

laminas dep should be not needed if this translates to a few echo/header/http_response_code lines

I see the PR #1671 which remove/assert that there is no global sticky.
i think in App __construct, if not injected via $defaults['request'], we create a Request using nyholm/psr7-server and all sticky + $_GET/$_POST/$_FILES that are already present somewhere in the app must point to App->request, what you think?

But before this i need to understand why demos, except for SSE, works perfect, but not in tests.

[mvorisek]

request must be handled as PSR request as well
laminas dep should be not needed if this translates to a few echo/header/http_response_code lines

I replace with code, but because of the small difference in performance, I always prefer the ready-made solutions, which are already tested in almost every situation, even those we don't know at the moment.

replacing literaly no more than several lines and doubling the non-dev dependencies, is IMHO really not helpful

[mvorisek]

ui/src/App.php

Line 1119 in beb149f

exit(1);

Are you sure that this cannot be changed to an Exception or other ways to not force exit the process?
My fear is that if you use Atk4 in a routing/handler contest, that exit in place of an Error will stop the flow without an output, without running post route middleware or logging of the error, without considering that to avoid that line you must override via copy/paste the whole method just to remove it.

can be put into a protected method that can be overriden with a custom exit handler, but as described, it is too late to have a full control of the output as partly sent already

[mvorisek]

to be reintroduced in #2009

[mvorisek]

Thank you @abbadon1334 ❤️