Weave Code
Protocol Laravel Package
hoa/protocol
Hoa\Protocol is a PHP library for abstracting resource access through a hierarchical protocol system. It lets you register custom protocols and resolvers, then resolve paths such as hoa:// or app:// to real resources, simplifying flexible file and stream handling.
hoa/protocol is a PHP library for defining and resolving custom protocol trees, letting applications address resources through readable protocol-style paths instead of hard-coded filesystem locations. It is useful for building flexible resource resolution layers and integrating with the wider Hoa ecosystem.
- Build hierarchical protocol trees with named nodes and aliases.
- Resolve paths through registered protocols such as
hoa://. - Register custom protocols and fallback locations.
- Keep resource routing decoupled from concrete paths.
Frequently asked questions about Protocol
- Is hoa/protocol a Laravel package?
- No. hoa/protocol is a low-level PHP library from the Hoa project that abstracts resources behind custom protocols and provides a unified hoa:// stream wrapper. It ships no Laravel service provider, facade, config publishing, or package auto-discovery, and it does not integrate with Laravel's container, configuration, or Flysystem-based filesystem abstraction. Treat it as a generic Composer dependency that requires manual wiring if you bring it into a Laravel app.
- Can I install hoa/protocol in a Laravel application with Composer?
- It is technically installable through Composer if your PHP version satisfies the package's constraints, but integration is entirely manual. You would need to register the stream wrapper yourself, typically in a service provider, and manage ordering relative to the rest of your application bootstrap. There is no documented Laravel usage, so expect to write and own all of the glue code.
- Does hoa/protocol support modern Laravel and PHP versions?
- That is unproven. The last release was January 2017 and the repository is archived, so compatibility with current PHP and Laravel versions has not been validated by upstream. Before committing, run a spike that checks exact Composer constraints, autoloading, and transitive Hoa dependencies against your target stack. Pin the exact version and expect possible conflicts.
- What is the hoa:// stream wrapper used for?
- It gives PHP code a single hoa:// scheme that resolves paths through registered protocols and mapped resource trees. That lets code address files, packages, and application data through one consistent, relocated-friendly path syntax instead of hardcoded absolute paths. The value only shows up if you actually need that protocol-abstraction semantics, which is unusual in a typical Laravel codebase.
- Is hoa/protocol still maintained?
- No. The repository is archived, the last release dates to January 2017, and there is no active security or maintenance process. Dependency scanners will likely flag it as abandoned, and any bug or CVE would have to be handled by your own team. Budget for vendoring, patching, and eventual removal rather than expecting upstream fixes.
- What are Laravel-native alternatives to hoa/protocol?
- Most use cases map to Laravel's Storage and Flysystem abstraction, path helpers like base_path and storage_path, URL and asset helpers, and config-driven path resolution. For protocol-style behavior you can also register your own stream wrapper or build a small resolver service bound in the container. These options are supported, documented, and understood by Laravel developers, which matters more than the abstraction purity hoa/protocol offers.
- What are the production risks of hoa/protocol's global stream wrapper?
- Stream wrapper registration is global and order-sensitive, so behavior can differ between web requests, CLI commands, queue workers, and tests depending on bootstrap order. That makes failures non-obvious and hard to reproduce. Combined with an archived upstream and old transitive Hoa dependencies, the operational risk is high. Prove startup ordering in every runtime context before relying on it, or isolate it behind an adapter.
- How do I migrate a Laravel app away from hoa:// paths?
- Start by inventorying every hoa:// and custom protocol usage and identifying who owns each call site. Wrap the package behind an application-owned interface, bind it in a service provider, and add characterization tests that lock in current behavior. Then migrate call sites incrementally to Laravel paths, Storage, Flysystem, or explicit configuration, using parallel-run or fallback behavior for business-critical paths. Finish by removing the dependency and documenting the decommissioning.
- How should I isolate hoa/protocol if legacy compatibility requires it?
- Treat it as a temporary compatibility bridge, not a strategic dependency. Put it behind an internal interface so no domain logic or public API depends on hoa:// directly, bind that adapter in a service provider, and cover it with characterization tests. Pin the exact version, consider a private fork or Composer patch for fixes, and assign clear ownership plus an exit plan.
- Should I adopt hoa/protocol for a new Laravel project?
- Generally no. Laravel already provides path resolution, filesystem abstraction, configuration, and URL generation, so adding hoa/protocol creates a parallel low-level abstraction most Laravel developers will not recognize. For greenfield work, skip it unless there is a hard compatibility requirement you cannot meet natively. Even then, scope it narrowly behind an adapter from day one.
Weaver
How can I help you explore Laravel packages today?