Protocols - Pawabase

Services → Realtime → Protocols shows what a client can connect with today, and what is still on the roadmap, honestly rather than hidden.

Protocols page with six cards — Realtime → Protocols: WebSocket and Server-Sent Events are live; the others are marked not yet available.

Protocol	Status	What it does
WebSocket	Live	Full duplex: subscribe, publish, presence and history replay all go over one socket. The client libraries use this
Server-Sent Events	Live	One-way: subscribe to one or more channels and receive messages and presence changes as events on the stream. Publishing goes through a plain HTTP publish call
MQTT	Not yet available	A publish/subscribe protocol used by IoT and embedded clients
MQTT over WebSocket	Not yet available	MQTT framed over a WebSocket, for browser MQTT clients
HTTP streaming	Not yet available	Chunked-transfer streaming without SSE’s event framing
Long polling	Not yet available	A fallback for clients that cannot hold a streaming connection open

Each live card shows the address to connect to and has a copy button.

Which to use

Your app, chat, presence, collaboration: WebSocket. pawabase.realtime.channel(...).subscribe() does it for you.
Listen-only, dashboards, servers, strict proxies: Server-Sent Events: pawabase.realtime.stream([...]) (pb.realtime.sse([...])).
Sending without a connection: pawabase.realtime.publish(...), a plain HTTP call.

Other languages

Anything that can open a WebSocket or an SSE stream can use realtime. Authenticate with your publishable key and, for a signed-in person, their access token. The same channel rules apply to every protocol.

Connection

Client behaviour.

Channel rules

Rules apply to every protocol.