On Sun, Dec 10, 2017 at 3:49 PM, John Porter <j...@designermonkey.co.uk> wrote:
> When I first read the name change, I assumed that it meant that any class > I write (like a route class) is supposed to implement this to be used in a > middleware, that I would have to choose for each middleware which class to > use to create a response object. I hope that I am wrong and think that is > the case. > > That got me thinking then, well, what is it? What is it supposed to do? > How do I implement something like that? Basically the same questions I've > asked of this proposal from the start. > I'm a little surprised that this isn't intuitive. Perhaps that is a failing of the meta document? The request handler is the "final" processing that will determine what response is suitable for a given request. Within a middleware stack, this typically means passing the request off to the next middleware as many times as necessary, until domain gateway is reached and actually handles the request. It is not expected that users will need to implement the request handler, since it is typically part of a given middleware dispatching system. You might want to take a look at an implementation of PSR-15 such as Zend Expressive or https://github.com/northwoods/broker Hopefully this clarifies things. -- Woody Gilk http://about.me/shadowhand -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAGOJM6JfrKWh6WLBZWoxoNJ9_RJSdXsJouC79RsxGzGZaaVU9g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
