Streaming Behavior

The streaming methods provide live data. They do not replay historical data.

Streams stay open until:

• the client cancels the call

• the network connection fails

• the server restarts or shuts down

• the client process exits

Always cancel streams explicitly when you are done with them. This releases server-side resources and avoids unnecessary buffering in your client.

Dropped Counters

dropped_reports and dropped_frames are absolute counters. Monitor them for increases between consecutive messages. If a counter increases, the client or network path could not consume the full stream quickly enough.

To reduce dropped data:

• add sensor, aircraft, or downlink-format filters

• avoid processing-heavy work inside the stream receive loop

• decouple receiving from downstream processing with a local queue

• consume only the stream you need