The picture from StackPHP is missing the third case from 5.1 Middleware 
Design section:

The middleware may: (...) Create and return a response without passing it 
> to the delegate, thereby preventing any further middleware from processing.
>

BTW - the wording there is also imprecise - middleware can not pass a 
response to the delegate. I will make a pull request for that.



On Friday, March 24, 2017 at 4:56:23 PM UTC+1, Woody Gilk wrote:
>
> I reached out to StackPHP to see if we could reuse their image, which more 
> simple but essentially the same http://stackphp.com/img/onion.png
>
>
>
> --
> Woody Gilk
> http://about.me/shadowhand
>
> On Thu, Mar 23, 2017 at 5:21 PM, Tomasz Darmetko <isi...@gmail.com 
> <javascript:>> wrote:
>
>> The best illustration of a middlewares arrangement I can find is this one 
>> <https://dab1nmslvvntp.cloudfront.net/wp-content/uploads/2013/02/middleware.jpg>,
>>  
>> from the article Working with Slim Middleware. 
>> <https://www.sitepoint.com/working-with-slim-middleware/> Maybe we 
>> should include such an illustration in the Meta Document? One picture is 
>> worth many words. We could ask the author to make the illustration 
>> available on CC license. Eventually even I could try to create one on CC 
>> license.
>>
>>
>> On Thursday, March 23, 2017 at 10:48:55 PM UTC+1, Woody Gilk wrote:
>>>
>>> On Thu, Mar 23, 2017 at 4:28 PM, Tomasz Darmetko <isi...@gmail.com> 
>>> wrote:
>>>
>>>> I'm trying to understand how does the pipeline pattern fits into 
>>>> proposed concept of middleware and I'm failing to see the connection.
>>>
>>>
>>> That's probably fair. At some point in the past I had a diagram that 
>>> helped illustrate what the intention of this sentence meant. 
>>>
>>> Do you know of a pattern that applies to how middleware operates?
>>>
>>> --
>>> 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+u...@googlegroups.com <javascript:>.
>> To post to this group, send email to php...@googlegroups.com 
>> <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/php-fig/c1c7408c-4792-4115-a371-cd305cda128d%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/php-fig/c1c7408c-4792-4115-a371-cd305cda128d%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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/fa8ad2e4-3cb9-4d9f-9e2e-d4bc421c0844%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to