Client and backend. Every class listed here is shared: the same code is compiled into your app and into your server. The package's page in the client API lists all of it, including any classes that exist only in the app.

package com.codename1.realtime

Real-time threads: periodic work released on time, at a fixed operating-system priority, that the garbage collector does not stop.

A RealtimeTask runs on its own RealtimeThread. Its setup() runs once and may allocate; after it, every period wakes the thread and runs cycle(), which must not allocate. That rule is what lets the thread run beside a collector: it is checked when the application is built, and again while it runs. See Realtime for the entry point, what each platform provides and what the guarantees are.

Types

annotation AllocationAllowedMarks a method that a RealtimeTask’s cycle() may call although it allocates.
class RealtimeEntry point to real-time threads: periodic tasks that run at a fixed operating-system priority, are released on an absolute clock, and are not paused by the garbage collector.
class RealtimeAllocationErrorThrown out of a RealtimeTask’s cycle() when the cycle allocates beyond its budget (RealtimeParameters.setAllocationBudget(int), zero unless set).
class RealtimeParametersHow a RealtimeThread is scheduled: its period, its operating-system priority, the CPU it runs on and how much it may allocate per period.
class RealtimeStatisticsA snapshot of how a RealtimeThread’s periods went: how late each release woke the thread (latency), how long its cycles ran, and how many releases it missed.
class RealtimeTaskThe work a RealtimeThread runs every period.
class RealtimeThreadA thread that runs a RealtimeTask once per period.