On Tuesday, May 9, 2017 at 4:54:25 PM UTC-5, Alessandro Pellizzari wrote:
>
> On 09/05/17 21:11, Rasmus Schultz wrote:
>
> > I'd like to encourage anyone reading this to please post the biggest,
> > most complex middleware stack they've ever used. Just the stack, not the
> > implementations or individual component bootstrapping necessarily. Let's
> > see what we're really dealing with?
>
>From my example earlier, my effective stack of middleware was:
NikicFastRoute::class, // routing
FixBrokenDiactorosCookieHeaderBehaviour::class, // workaround until a
cookie fix to diactoros could be tagged
CorsCompletelyOpenForDevelopment::class, // utility middleware that was
soon to be swapped for a better proper impl
UserAuthentication::class, // ensured that the request was made by an
authenticated user
OrganisationAuthorization::class, // ensured that the authenticated
user was authorized to access organisation resources
UserIdMetadataEnrichment::class, // used to ensure that the
authenticated user would be added to event envelopes
ResponseAssertion::class, // make sure that by this point any
non-response views returned were now responses
ViewTransformer::class, // transform non-response values into responses
ActionHandler::class, // dispatcher
The first and last middleware were provided by the underlying framework and
the other middleware were added as a part of the application itself.
--
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/576da415-5830-4c83-a74a-ecb85bb40b34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
