PHPackages psg/sr2-implementation - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [HTTP & Networking](/categories/http) 4. / 5. psg/sr2-implementation ActiveLibrary[HTTP & Networking](/categories/http) psg/sr2-implementation ====================== App Standardization Prototype 0.1(4y ago)03MITPHPPHP >=5.3.0 Since Jul 15Pushed 4y ago1 watchersCompare [ Source](https://github.com/PHP-SG/sr-2-implementation)[ Packagist](https://packagist.org/packages/psg/sr2-implementation)[ Docs](https://github.com/php-sg/sr-2-implementation)[ RSS](/packages/psg-sr2-implementation/feed)WikiDiscussions master Synced 1w ago READMEChangelogDependencies (2)Versions (2)Used By (0) PSG SR 2 Implementation ======================= [](#psg-sr-2-implementation) ``` composer require psg/sr2-implementation ``` The intent of this implementation is to give a well documented prototype of how LayeredApp can be implemented. The complexity of integrating normal middleware with frontware and backware has, to my knowledge, prevented this from ever being done. Notes ----- [](#notes) In my implementation, I provide the callable with the parameters ($request, $response, $app). It is, however, expectable that frameworks will want to: - inject parameters as necessary into the core call - inject parameters into the \_\_construct if the core is an instantiable As such, the parameters are left up to the framework. ### Possible Improvements [](#possible-improvements) - just in time middleware construction with dependency injection to \_\_construct - add exception if a ware is added after it's stage has passed Use --- [](#use) To see all the layers, which are set to echo to announce themselves and each add a header ``` use Psg\Sr1\Implementation\Factory\Sr1Factory; use Psg\Sr2\Implementation\{Beforeware, Frontware, Middleware, Backware, Afterware, LayeredApp}; $core = function($request, $response, $app){ echo "Request Headers:\n"; var_export($request->getHeaders()); echo "\nadding body\n"; return $response->withBodyString("\nBODY\n"); }; $App = new LayeredApp; $App->add(new Beforeware); $App->add(new Frontware); $App->add(new Middleware); $App->add(new Middleware); $App->add(new Backware); $App->add(new Afterware); $App->core($core); $Factory = new Sr1Factory(); $request = $Factory->createServerRequest('GET', 'http://bobery.com'); $App->handle($request); /*> Before Front Middle wrap1{ Middle wrap2{ Request Headers: array ( 'Host' => array ( 0 => 'bobery.com', ), 'frontware' => array ( 0 => '1', ), 'middleware' => array ( 0 => '1', 1 => '2', ), ) adding body }wrap2 }wrap1 Back ==========RESPONSE {============= array ( 'middleware' => array ( 0 => '2', 1 => '1', ), 'Backware' => array ( 0 => '1', ), )wrap1{ wrap2{ BODY }wrap2 }wrap1 ==========} RESPONSE============= After */ ``` To see the ability to exit at certain phases ``` # Exit in frontware $App = new LayeredApp; $App->add(new Beforeware); $App->add(new Frontware(['exit'=>true])); $App->add(new Middleware); $App->add(new Middleware); $App->add(new Backware); $App->add(new Afterware); $App->core($core); /*> Before Front Back ==========RESPONSE {============= array ( 'exit_at' => array ( 0 => 'frontware', ), 'Backware' => array ( 0 => '1', ), ) ==========} RESPONSE============= After */ # Exit in middleware $App = new LayeredApp; $App->add(new Beforeware); $App->add(new Frontware); $App->add(new Middleware(['exit'=>true])); $App->add(new Middleware); $App->add(new Backware); $App->add(new Afterware); $App->core($core); /*> Before Front Middle Back ==========RESPONSE {============= array ( 'exit_at' => array ( 0 => 'middleware id 1', ), 'Backware' => array ( 0 => '1', ), ) ==========} RESPONSE============= After */ ``` ### Health Score 18 — LowBetter than 8% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity3 Limited adoption so far Community7 Small or concentrated contributor base Maturity36 Early-stage or recently created project Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Unknown Total 1 Last Release 1768d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/4543facab3c88d548b98d8472b532faf7bcd00555cc47c0dc808d935f8d3d73f?d=identicon)[grithin](/maintainers/grithin) --- Top Contributors [![grithin](https://avatars.githubusercontent.com/u/7241358?v=4)](https://github.com/grithin "grithin (3 commits)") --- Tags httpresponserequesthttp-messagefactorysr-2 ### Embed Badge ![Health badge](/badges/psg-sr2-implementation/health.svg) ``` [![Health](https://phpackages.com/badges/psg-sr2-implementation/health.svg)](https://phpackages.com/packages/psg-sr2-implementation) ``` ### Alternatives [psr/http-message Common interface for HTTP messages 7.1k1.0B5.5k](/packages/psr-http-message)[psr/http-factory PSR-17: Common interfaces for PSR-7 HTTP message factories 1.9k692.9M1.9k](/packages/psr-http-factory)[fig/http-message-util Utility classes and constants for use with PSR-7 (psr/http-message) 39489.0M274](/packages/fig-http-message-util)[chillerlan/php-httpinterface A PSR-7/17/18 http message/client implementation 1417.1k5](/packages/chillerlan-php-httpinterface)[art4/requests-psr18-adapter Use WordPress/Requests as a PSR-18 HTTP client 153.3k](/packages/art4-requests-psr18-adapter) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)