Application engines

Engine provides shared primitives; select an HTTP or WebSocket application engine. Their manifests conflict because request/response aliases and runtime assumptions differ.

• HTTP engine with the Web scaffold and verified minimal JSON route.
• WebSocket engine with known integration gaps.

Install the chosen engine through a compatible scaffold/lock. A transport supported by Server does not automatically become a completed framework feature.

Source reviewed 2026-10-17; Ivan Zorin / Localzet Group. Guide AGPL-3.0-or-later; package licenses retained.