- What is hoa/http used for in PHP?
- Hoa\Http is a modular standalone PHP library for modeling and manipulating HTTP requests and responses. It supports constructing, parsing, and serializing HTTP messages and provides client-side sending and server-side handling over Hoa sockets and streams. It separates HTTP semantics from transport concerns and is not a full framework.
- Is hoa/http a Laravel package?
- No. hoa/http is part of the modular Hoa project and is not designed as a Laravel package. It does not provide Laravel service container integration, facades, Illuminate request/response lifecycle support, Symfony HttpFoundation integration, PSR-7 or PSR-18 compliance, or Laravel auto-discovery. Using it in Laravel requires an adapter or isolated integration.
- How do I install hoa/http with Composer?
- You can install it through Composer if the package resolves on your PHP version, typically with a require command for hoa/http. Because it is archived and has no Laravel auto-discovery, you must validate autoloading and PHP constraints yourself. Pin the exact version or vendor and fork it if you proceed.
- Does hoa/http support Laravel 10 or Laravel 11?
- There is no tested compatibility matrix for modern Laravel versions in the provided context. The package was last released in 2017 and is archived, so Laravel 10 or 11 support is unproven. Run a time-boxed proof of concept against your actual Laravel and PHP matrix before assuming compatibility.
- Is hoa/http compatible with PHP 8?
- PHP 8.x compatibility is not demonstrated by the available information. The package is archived and dates to 2017, so you should validate Composer constraints, extensions, and runtime behavior under your target PHP version. Treat it as incompatible until proven in CI.
- Does hoa/http support PSR-7 or PSR-18?
- The evaluation notes unclear PSR compliance, and hoa/http does not appear designed around PSR-7 or PSR-18. You should expect custom adapters if you need PSR-compatible messages or clients. For standard PSR needs, a maintained PSR-7 or PSR-18 implementation is safer.
- Is hoa/http safe to use in production?
- The technical risk is high because the package is archived and unmaintained, with no security patches or upstream compatibility fixes. It is not a strategic dependency for a normal Laravel production application. If a narrow capability justifies it, isolate it behind an internal interface, vendor or fork it, add contract tests, and complete security and license review first.
- What are alternatives to hoa/http for Laravel HTTP clients?
- For standard outbound HTTP in Laravel, prefer Laravel's HTTP client, Guzzle, Symfony HttpClient, or a maintained PSR-7 or PSR-18 implementation. Map the exact required behavior first, because most HTTP client and message modeling needs can be met without Hoa. Use hoa/http only if a genuinely unique capability cannot be replaced.
- How do I integrate hoa/http into a Laravel application?
- Treat hoa/http as an isolated infrastructure detail rather than a first-class Laravel dependency. Wrap it behind an internal interface or adapter so controllers, jobs, and domain services do not reference Hoa types directly. Pin or vendor the dependency, add contract tests around the behavior Laravel depends on, and run a proof of concept in a non-production branch.
- Is hoa/http maintained, and what is the exit plan if it breaks?
- hoa/http is archived, was last released in 2017, has 10 stars, and shows 0 dependents, so assume no upstream maintenance. Budget internal ownership for fixes and security patching, or reject the dependency. Any exit plan should include an adapter boundary, a replacement implementation with a maintained library, and parallel or shadow validation before broad rollout.