Add native WebSocket support (client and/or server) to LSL, similar to the existing HTTP request capabilities (llHTTPRequest, llRequestURL, etc.).

WebSockets would allow persistent, bidirectional connections so scripts can send and receive real-time messages far more efficiently than the current HTTP polling or short-lived request model. This would greatly improve responsiveness for chat systems, multiplayer game logic, external service integration, dashboards, and any use case that needs low-latency updates.

Any additional details...

Support both outbound WebSocket clients (llWebSocketConnect or similar) and optional inbound/listening capability.

Events for open, message, close, and error (e.g. websocket_message, websocket_close).

Ability to send text and optionally binary frames.

Reasonable connection limits, timeouts, and memory safeguards consistent with other LSL networking features.

Optional authentication/header support and TLS (wss://).

Compatibility with existing HTTP features so creators can migrate gradually.

This would significantly reduce server load and script complexity compared to repeated HTTP requests while enabling true real-time experiences in Second Life.