Download the PHP package psr-discovery/http-factory-implementations without Composer

Lightweight library that discovers available PSR-17 HTTP Factory implementations by searching for a list of well-known classes that implement the relevant interface, and returns an instance of the first one that is found.

This package is part of the PSR Discovery utility suite, which also supports PSR-18 HTTP Clients, PSR-14 Event Dispatchers, PSR-11 Containers, PSR-6 Caches and PSR-3 Logs.

This is largely intended for inclusion in libraries like SDKs that wish to support PSR-17 Factories without requiring hard dependencies on specific implementations or demanding extra configuration by users.

• Requirements
• Implementations
• Installation
• Usage
• Handling Failures
• Exceptions
• Singletons
• Mocking Priority
• Preferring an Implementation
• Using a Specific Implementation

Requirements

• PHP 8.2+
• Composer 2.0+

Successful discovery requires the presence of a compatible implementation in the host application. This library does not install any implementations for you.

Implementations

The following psr/http-factory-implementation implementations are discovered and instantiated automatically:

• guzzlehttp/psr7 ^2.0
• http-interop/http-factory-guzzle ^0.2 | ^1.0
• httpsoft/http-message ^1.0.4
• laminas/laminas-diactoros ^2.0
• nimbly/capsule ^2.0
• nyholm/psr7 ^0.2.2 | ^1.0
• slim/psr7 ^1.0
• tuupola/http-factory ^1.0.2
• typo3/core ^10.1 | ^11.0 | ^12.0
• zendframework/zend-diactoros ^2.0

The following mock implementations are also available:

• psr-mock/http-factory-implementation ^1.0

If a particular implementation is missing that you'd like to see, please open a pull request adding support.

Installation

Usage

Handling Failures

If the library is unable to discover a suitable PSR-17 implementation, the Discover::httpRequestFactory(), Discover::httpResponseFactory() or Discover::httpStreamFactory() discovery methods will simply return null. This allows you to handle the failure gracefully, for example by falling back to a default implementation.

Example:

Singletons

By default, the Discover::httpRequestFactory(), Discover::httpResponseFactory() or Discover::httpStreamFactory() methods will always return a new instance of the discovered implementation. If you wish to use a singleton instance instead, simply pass true to the $singleton parameter of the discovery method.

Example:

Mocking Priority

This library will give priority to searching for a known, available mocking library before searching for a real implementation. This is to allow for easier testing of code that uses this library.

The expectation is that these mocking libraries will always be installed as development dependencies, and therefore if they are available, they are intended to be used.

Preferring an Implementation

If you wish to prefer a specific implementation over others, you can prefer() it by package name:

In this case, this will cause the httpRequestFactory() method to return the preferred implementation if it is available, otherwise, it will fall back to the default behavior. The same applies to httpResponseFactory() and httpStreamFactory() when their relevant classes are configured similarly.

Note that assigning a preferred implementation will give it priority over the default preference of mocking libraries.

Using a Specific Implementation

If you wish to force a specific implementation and ignore the rest of the discovery candidates, you can use() its package name:

In this case, this will cause the httpResponseFactory() method to return the preferred implementation if it is available, otherwise, it will return null. The same applies to httpRequestFactory() and httpStreamFactory() when their relevant classes are configured similarly.

This library is not produced or endorsed by, or otherwise affiliated with, the PHP-FIG.