Download the PHP package phpnomad/guzzle-fetch without Composer
On this page you can find all versions of the php package phpnomad/guzzle-fetch. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package guzzle-fetch
phpnomad/guzzle-fetch
Integrates guzzlehttp/guzzle with PHPNomad's phpnomad/fetch abstraction. The package ships a concrete FetchStrategy implementation backed by a GuzzleHttp\Client, so any application code that constructor-injects PHPNomad\Fetch\Interfaces\FetchStrategy can make outbound HTTP requests through Guzzle without touching Guzzle directly.
This is the transport you want in non-WordPress runtimes where wp_remote_request is not available: CLI tools, SaaS backends, worker processes, and any PHPNomad application that prefers Guzzle to the WordPress HTTP API.
Installation
What This Provides
PHPNomad\Guzzle\FetchIntegration\Strategies\FetchStrategyimplementsPHPNomad\Fetch\Interfaces\FetchStrategy. It holds aGuzzleHttp\Client, reads the URL, method, headers, body, and query params off the incomingFetchPayload, and forwards them toClient::request(). Guzzle exceptions are converted toPHPNomad\Rest\Exceptions\RestExceptionwith the upstream status code preserved when available.PHPNomad\Guzzle\FetchIntegration\Models\ResponseimplementsPHPNomad\Http\Interfaces\Response. The strategy populates it from the Guzzle response and returns it to callers, so downstream code sees the same interface regardless of the underlying transport.PHPNomad\Guzzle\FetchIntegration\Initializeris the loader hook that binds the strategy to theFetchStrategyinterface in the DI container.
Requirements
phpnomad/fetch, the HTTP abstraction this package implements.guzzlehttp/guzzle, the HTTP client this package bridges.
The package also pulls in phpnomad/http, phpnomad/rest, phpnomad/di, and phpnomad/loader as part of the standard PHPNomad integration surface.
Usage
Registration goes through phpnomad/loader. Add new Initializer() to the list of initializers your application passes to the Bootstrapper, and the container will bind the Guzzle-backed strategy to PHPNomad\Fetch\Interfaces\FetchStrategy during boot.
Once the bootstrapper has run, any service that declares FetchStrategy as a constructor argument receives the Guzzle-backed implementation. No further configuration is required for the default case. If you need custom Guzzle middleware, a base URI, or a preconfigured client, subclass the strategy and bind your subclass to the interface in your own initializer.
Documentation
Full PHPNomad documentation lives at phpnomad.com. Guzzle's own documentation lives at docs.guzzlephp.org.
License
Released under the MIT License.
All versions of guzzle-fetch with dependencies
phpnomad/di Version ^2.0
phpnomad/loader Version ^1.0 || ^2.0
guzzlehttp/guzzle Version ^7.9
phpnomad/fetch Version ^1.0
phpnomad/http Version ^1.0