README

The Atomic Repository is the smallest possible unit of granularity. It enforces a strict architectural boundary through the following rules:

1. No Subdirectories: Only one level of directory inside src/.
2. Maximum 10 Files: Only 10 files per package.
3. Strict Typing: Mandatory declare(strict_types=1) and full type hinting for all properties and methods.
4. Object Calisthenics: Maximum of 50 lines per class and 2 instance variables to ensure extreme cohesion.
5. Value Objects: All primitives must be wrapped. Raw strings or integers are not permitted in domain logic.
6. First Class Collections: Arrays are forbidden for data transport; use dedicated Collection objects.
7. Tell, Don't Ask: Getters and setters are prohibited. Objects must expose behavior, not state.
8. Infrastructure Ignorance: The domain core is decoupled from persistence, frameworks, and external tools.
9. Logic Flow: The else keyword is banned. Use guard clauses and early returns to minimize indentation.

Installation

Install the package via composer:

composer require phprise/http-connector

Usage

The http-connector is the Orchestrator of the HTTP system. It connects the specialized request atoms to the client atoms, acting as the main entry point for sending data through the pipe.

Standard Connector

The synchronous connector uses a Psr\Http\Client\ClientInterface to send requests.

use Phprise\Http\Connector\Connector;

$connector = new Connector($client);
$response = $connector->send($request);

Async Connector

The asynchronous connector uses an Http\Client\HttpAsyncClient to return promises.

use Phprise\Http\Connector\AsyncConnector;

$connector = new AsyncConnector($asyncClient);
$promise = $connector->send($request);

Evented Connector

A decorator that adds PSR-14 event support to the standard connector.

use Phprise\Http\Connector\EventedConnector;

$connector = new EventedConnector($standardConnector, $eventDispatcher);
$response = $connector->send($request);

Note

This atom is responsible only for orchestration. It does not know how to build a request or how to transmit bytes; it only delegates these tasks to specialized atoms.

Philosophy

We follow The OTAKU Manifesto: Fluid Structure Design.

1. O - Own your Discipline (Be strict with yourself)
2. T - Tools for Composition (Compose like Unix)
3. A - Armor the Core (Protect the heart of the business)
4. K - Keep Infrastructure Silent (Infrastructure is just a detail)
5. U - Universal Language & Contracts (Speak the user's language via clear contracts)

Please read more about it in PHILOSOPHY.md.

License

MIT License

Free to use, modify, and distribute.