[feature request] some way to provide custom middleware

[Zydnar]

I don't know how much would it be helpful, but it's just an idea. Between request and response is now this 'request' function$server = new HttpServer([$requestLoop, 'request']); - but if sombody would need some logger function, trigger some event, gzip response etc. now it's required to use classes from this library src and write own custom bin file. It would be simplier to provide path to php file / config file with custom middleware returning request and continue this chain to send response or if returning response break this chain. The idea definitely would make this library more elastic. The idea I took from here: https://sailsjs.com/documentation/concepts/middleware - yes it's node library but the idea to process request is the same. So my idea is to provide default config like this and if needed way to overwrite it like --custom-middleware <path>.

[jdomenechb]

I find your proposal interesting to consider. The approach might be further discussed though.

A similar approach was taken for developing the library: the library builds the binary from the public/index.php in the Symfony project root. This was intended to provide some flexibility, but is an approach that I am not very fond of. I finally implemented it this way to allow developers with custom index.php files to mantain their custom Kernel setup.

I intended to later replace that behavior in a later version of the library, depending in how needed it was.

Your proposal in some way sounds very similar. I think adding middleware is interesting, but I am confident that an approach that satisfies both points of view could be found too.

For now, you could achieve some of the features you want to cover with this proposal with Symfony. For example, implementing en EventListener that listens on errors, or modifies the response in some way before being answered. More info in: https://symfony.com/doc/current/reference/events.html and https://symfony.com/doc/current/event_dispatcher.html .