Search Results for "stream"

...Interactive JSON documents that can be edited and observed. Changes are persisted and synced across clients and saved in cache/storage. Clients can register functions to be called by other clients. deep stream will smartly route requests and responses. Query deep stream for online users and subscribe to login/logout events. Let your services be told whenever a new topic is subscribed to, letting you serve realtime data on demand.

tokio-tungstenite is a Rust library that connects the Tungstenite WebSocket implementation with the Tokio asynchronous runtime. It lets developers build non-blocking WebSocket clients and servers using Tokio’s async networking model. The crate wraps asynchronous TCP streams and upgrades them into WebSocket streams that integrate naturally with Rust futures and async tasks. It is useful for real-time services, streaming applications, chat systems, gateways, backend infrastructure, and any...

...The plugin is included by default in OBS Studio 28 and newer, so most modern OBS users do not need a separate installation. It exposes a structured request, response, and event protocol that can be used by dashboards, stream decks, bots, automation scripts, remote controllers, and broadcast systems. obs-websocket is especially useful for streamers, developers, live-event teams, and studios that need programmable control over OBS. It turns OBS from a manual desktop tool into an automation-ready production engine.

This is an attempt to provide very easy-to-use Lua Application Server working over WebSockets protocol (RFC 6455). LAppS is an application server for micro-services architecture. It is build to be highly scalable vertically. The docker cloud infrastructure (kubernetes or swarm) shall be used for horizontal scaling. LAppS has most scallable WebSockets server out there. LAppS is the same thing to WebSockets as the Apache or Nginx are to HTTP. LAppS does not supports HTTP (though it supports...

FluxyChat is a multi-tenant realtime chat API built on Cloudflare Workers, Durable Objects, and D1. What's different: - One Durable Object per room: WebSocket fan-out + ordering at the edge, no socket fleet to manage - Agent tool calls stream on the same room WebSocket as chat messages — debuggable in the operator console - MIT self-host on your own Cloudflare account, or use the hosted beta - Next.js operator console: rooms, agents, billing hooks out of the box - @fluxy-chat/sdk: TypeScript SDK with React hooks, reconnect/backoff, REST history pagination Built for SaaS teams adding in-app chat without Pusher-scale bills or running persistent WS pods.