Download the PHP package rapp-lib/middleman without Composer

mindplay/middleman

Dead simple PSR-15 / PSR-7 middleware dispatcher.

Provides (optional) integration with a variety of dependency injection containers compliant with container-interop.

To upgrade from 1.x to 2.x, please see UPGRADING.md.

Let's stop trying to make this complicated:

For simplicity, the middleware stack itself is immutable - if you need a stack you can manipulate, array, ArrayObject, SplStack etc. are all fine choices.

If you prefer implementing middleware as a reusable class, just implement __invoke() with the correct callback signature - or, optionally, implement MiddlewareInterface, like this:

Note that this works with or without implements MiddlewareInterface, as long as you get the callback signature right.

If you want to wire it to a DI container you can add a "resolver", which gets applied to every element in your middleware stack - for example:

Note that the "resolver" is any callable with a signature like function (string $name) : MiddlewareInterface - if you want the Dispatcher to integrate deeply with your framework of choice, you can use a custom resolver closure.

If you want to understand precisely how this component works, the whole thing is just one class with a few lines of code - if you're going to base your next project on middleware, you can (and should) understand the whole mechanism.

Middleware?

Middleware is a powerful, yet simple control facility.

If you're new to the concept of middleware, the following section will provide a basic overview.

In a nutshell, a middleware component is a function (or MiddlewareInterface instance) that takes an incoming (PSR-7) RequestInterface object, and returns a ResponseInterface object.

It does this in one of three ways: by assuming, delegating, or sharing responsibility for the creation of a response object.

1. Assuming Responsibility

A middleware component assumes responsibility by creating and returning a response object, rather than delegating to the next middleware on the stack:

Middleware near the top of the stack has the power to completely bypass middleware further down the stack.

2. Delegating Responsibility

By calling $next, middleware near the top of the stack may choose to fully delegate the responsibility for the creation of a response to other middleware components further down the stack:

Note that exhausting the middleware stack will result in an exception - it's assumed that the last middleware component on the stack always produces a response of some sort, typically a "404 not found" error page.

3. Sharing Responsibility

Middleware near the top of the stack may choose to delegate responsibility for the creation of the response to middleware further down the stack, and then make additional changes to the returned response before returning it:

The middleware component at the top of the stack ultimately has the most control, as it may override any properties of the response object before returning.