Connections & protocols
Full-duplex
Full-duplex communication allows both ends of a connection to send data independently, without waiting for a request-response turn for each message.
Also found under: Bidirectional communication, Two-way connection
How it works
WebSocket provides this transport capability, but an application protocol still defines which messages each side may send. Bidirectional transport should not be confused with permission for any browser to publish arbitrary business events. Product APIs can intentionally separate client subscriptions from trusted server publishing.
In a Pubb integration
Pubb clients send subscription commands through WebSockets and receive realtime events on the same connection. Business events are published by a trusted backend through the documented HTTP API or server SDK.
Connect a clientA practical example
A browser can join a second channel while receiving events from its first channel. Creating a chat message still goes through your backend's validation and publishing path.