Triangle Engine WS
Engine WS connects Localzet Server's WebSocket transport to Triangle applications. It matches the HTTP upgrade request to a route, runs middleware to check the handshake, and invokes the route handler when a frame arrives.
Server owns the listener, WebSocket framing, event loop, and worker lifecycle. Engine provides application types and Fiber context. Engine WS adds callbacks, request context, and message-sending helpers.
Current version
The current release is 2.0.0. It targets PHP 8.1+, Engine 9, Router 2, Middleware 2, and Localzet Server 7.1+.
composer require localzet/server:^7.1 triangle/engine-ws:^2.0
composer show triangle/engine-ws
composer show triangle/engine
composer show localzet/server
composer check-platform-reqs
Version 1.x belongs to the previous Engine 8 / Server 4 compatibility set. See the compatibility guide for a direct comparison. Engine WS and Engine HTTP cannot be installed in one Composer project.
Guides
- Installation and a working WebSocket endpoint
- Handshake and message handling
- Architecture and configuration
- Security and operations
- Compatibility between 1.x and 2.x
- Tests and coverage limits
Limits
Connection maps and groups live in process memory and are not synchronized between workers or hosts. Use a separate broker or IPC component for cross-process fan-out. Engine WS does not provide distributed rooms, durable delivery, or a complete authentication system.
Read the Russian overview.

