mattjmattj/plux

Librairy for implementing a Flux-like one-direction flow architecture server-side

plux

, _(*1)

introduction

plux is a PHP library created to answer a simple question:, _(*2)

Does implementing a Flux-like, one-direction flow architecture server-side make any sense?, _(*3)

quick how-to

installation

composer require mattjmattj/plux

initialization

Somewhere in the bootstrap of your application/framework you need to call, _(*4)

\Plux\Plux::initialize();

Plux will then create a Dispatcher that will have to handle the Actions and pass them to your registerd Stores., _(*5)

stores

Stores are like the ones in Flux. They should do the business part according to an action that is given to them through their handle method. Note that using the handle method is just a shortcut provided by the StoreTrait, but any callable can be used with the Dispatcher., _(*6)

You must register your Stores to Plux and give them a name :, _(*7)

\Plux\Plux::addStore('Foo', new \My\Super\Store\Bar());

The name will allow other parts of your application to call, _(*8)

\Plux\Plux::getStore('Foo');

Stores are supposed to emit events whenever they perform an action. Plux depends on evenement/evenement to implement Store events., _(*9)

actions

Actions must be created and dispatched to allow registered Stores to do their job. Actions are composed of two elements:, _(*10)

• a type
• a data array

After creating an action, you must dispatch it :, _(*11)

$action = new \Plux\Action ('type', ['foo' => 'bar']);
\Plux\Plux::getDispatcher()->dispatch($action);

components

Theoretically everybody can listen to Store events, but to make things easier Plux provides a Component trait with a single render function. When render is called the Component should output whatever it needs to. This part is left very opened and you are not forced to use the Component trait at all., _(*12)

example

A small but complete example of implementation is available here, _(*13)

debate

You think that even in a per-request context like in PHP, implementing a one-direction flow architecture is a great idea? You think that it is absurd? Do not hesitate and leave a comment in the dedicated issue, _(*14)

license

plux is released under the FreeBSD License, _(*15)