When Push Is Not Enough

Real-Time Apps with Server PushModule 4The lesson guide, the walkthrough video, the knowledge check and the hands-on lab this sample was built from are on learnwisej.com — free, with an AI tutor in every lesson.

Open the course

This example is the Update Cadence panel of TicketOps Live. A simulated dashboard model changes every 50 ms; a refreshTimer applies one coalesced update per tick at the cadence you choose (250 ms / 1 sec / 5 sec); polling is tied to live mode; and the panel counts model events and applied updates separately. The model event never pushes: it counts itself and sets a dirty flag, and the timer decides when the user sees the result.

The source of this sample

iceteagroup/LearnWisej-SamplesReal-Time Server Push Course/Module 4

Browse this folder on GitHub

Or clone it: git clone https://github.com/iceteagroup/LearnWisej-Samples.git — then open TicketOpsLive.slnx in Visual Studio and press F5.

Run it

cd "LearnWisej-Samples/Real-Time Server Push Course/Module 4/TicketOpsLive"
dotnet run -f net10.0 --urls http://localhost:5304

Then open http://localhost:5304. (Visual Studio: open TicketOpsLive.slnx, press F5.) Keep the tab in front while comparing cadences: browsers throttle timers in background tabs.

What to try

Control	What you should see
Live mode ✔	the KPI tiles move once per second; EVENTS RECEIVED climbs about 20/s, UPDATES APPLIED 1/s
Cadence → 250 ms	four updates per second (about 5 events per update)
Cadence → 5 sec	one update every five seconds (about 100 events per update) — same information, a fraction of the traffic
Live mode ✘	the simulator, the timer and polling stop; the tiles keep the last snapshot

Polling fallback. Add "enableWebSocket": false to Default.json and restart: connectionLabel shows ○ Polling 1000 ms while live mode is on and the browser console logs one Wisej: Poll request. per second. With a WebSocket, polling is not requested (StartPolling is not ignored when a socket is up and would be pure cost).