You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ARCHITECTURE.md
+15-7Lines changed: 15 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -810,8 +810,11 @@ This section describes the HTTP communication architecture that differs from the
810
810
811
811
1.**Custom Request/Response Objects**: Models create and receive custom Request and Response objects specific to this library
812
812
2.**HttpTransporter**: A dedicated class that handles the translation between custom objects and PSR standards
813
-
3.**PSR Compliance**: The transporter uses PSR-7 (HTTP messages), PSR-17 (HTTP factories), and PSR-18 (HTTP client) internally
814
-
4.**No Direct Coupling**: The library remains decoupled from any specific HTTP client implementation
813
+
3.**HTTPlug Integration**: Uses HTTPlug's Discovery component for automatic detection of available HTTP clients and factories
814
+
4.**PSR Compliance**: The transporter uses PSR-7 (HTTP messages), PSR-17 (HTTP factories), and PSR-18 (HTTP client) internally
815
+
5.**No Direct Coupling**: The library remains decoupled from any specific HTTP client implementation
816
+
6.**Provider Domain Location**: HTTP components are located within the Providers domain (`src/Providers/Http/`) as they are provider-specific infrastructure
817
+
7.**Synchronous Only**: Currently supports only synchronous HTTP requests. Async support may be added in the future if needed
0 commit comments