@@ -1548,7 +1548,7 @@ timed blocking methods in classes from `java.util.concurrent.*` follow this conv
1548
1548
<a name =" external-interaction-schedule " ></a >
1549
1549
[ #] ( #external-interaction-schedule ) Tm.5. ** Tasks that should happen at a certain system time, UTC
1550
1550
time, or wall-clock time far in the future, or run periodically with a cadence expressed in terms of
1551
- system/UTC/wall-clock time (rather than internal machines 's CPU time) are * not* scheduled with
1551
+ system/UTC/wall-clock time (rather than internal machine 's CPU time) are * not* scheduled with
1552
1552
` ScheduledThreadPoolExecutor ` ?** ` ScheduledThreadPoolExecutor ` (this class is also behind all
1553
1553
factory methods in ` Executors ` which return a ` ScheduledExecutorService ` ) uses ` System.nanoTime() `
1554
1554
for timing intervals. [ ` nanoTime() ` can drift against the system time and the UTC time.] (
@@ -1564,7 +1564,7 @@ https://android.jlelse.eu/schedule-tasks-and-jobs-intelligently-in-android-e0b0d
1564
1564
1565
1565
<a name =" user-interaction-schedule " ></a >
1566
1566
[ #] ( #user-interaction-schedule ) Tm.6. On consumer devices (PCs, laptops, tables, phones),
1567
- ** ` ScheduledThreadPoolExecutor ` (or ` Timer ` ) is * not* used for human interaction tasks or
1567
+ ** ` ScheduledThreadPoolExecutor ` (or ` Timer ` ) is * not* used for human interaction tasks or
1568
1568
interactions between the device and a remote service?** Examples of human interaction tasks are
1569
1569
alarms, notifications, timers, or task management. Examples of interactions between user's device
1570
1570
and remote services are checking for new e-mails or messages, widget updates, or software updates.
0 commit comments