Thanks for your answer! the with(out)Middleware methods are what makes up the stack. This is making > general, what every implementation has but does differently. >
Yes but why do we need interoperability for that? I don't see the need for that (especially in a PSR for a middleware standard), this is not a problem today. > Would you agree with me that StackInterface should be at least an > extension of the FrameInterface? Like so you can combine stacks in other > stacks (without having to use a dumb StackWrapper class that implements > FrameInterface). > If middleware stacks or pipes or whatever were middlewares, then it would be easy to combine them. I don't see why we need a separate interface for "something that takes a request and returns a response" when we already have it (MiddlewareInterface). -- 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/cfef4f19-b045-4a3d-aa2e-5717a81e98eb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
