Real-time WebSocket

All dynamic data flows via push: vehicle positions, chat, alerts, notifications, presence. No polling — optimal bandwidth.

Push (zero polling) ACNT auth 30 s heartbeat

Enterprise architecture

What Real-time WebSocket does

Endpoint

WebSocket /ws/WebClient

Single endpoint for all push (positions, chat, alerts).

Auth

ACNT auth (6 params)

Cookie handshake + token-based via WsTokenAuth.

Heartbeat

Heartbeat & reconnect

PING/PONG every 30 s, auto-reconnect with exponential backoff.

Pool

Multi-server (pool)

LocalSocketClient relays events across app0, app1, iot0, iot1.

Events

Typed events

CHAT, RIDE, EV_SOS, EV_CHAT, STREAM_READY, …

Cross-app

The same WebSocket serves the FleetMan webclient + RN mobile apps.

Architecture

How it integrates

The WebSocket server uses a delimited text protocol with feature prefix:

// Connexion
wss://app0.malambi.net/ws/WebClient?acc_token=...

// Events serveur → client
CHAT|MSG|...
RIDE|NEW_REQUEST|...
EV_SOS|...
STREAM_READY|streamUrl|expiresAt

Technical specs

Endpoint	/ws/WebClient
Auth	ACNT (6 params)
Heartbeat	30 s PING/PONG
Reconnect	exponential backoff (max 30 s)
Multi-serveur	LocalSocketClient pool
Clients	WebClient ExtJS + RN apps

Try Real-time WebSocket on FleetMan

Bundled with FleetMan — activation is instant. Contact your account manager or start a free trial.

30-day free trial Back to FleetMan