Commit b6b60c6
committed
restart wait time on every OperationRepo.enqueue()
Every time something new is enqueued we will not restart waiting for
batches timer. The motivation is to prevent a misbehaving app from
continuously making network calls.
We are basically saying wait for the "the dust to settle" or
"the water is calm" to ensure the app is done making updates.
FUTURE: Highly recommend not removing this "the dust to settle" logic,
as it ensures any app stuck in a loop can't cause continuous network
requests. If the delay is too long for legitimate use-cases then allow
tweaking the opRepoExecutionInterval value or allow commitNow() with a
budget.1 parent 39a8b52 commit b6b60c6
File tree
1 file changed
+20
-10
lines changed- OneSignalSDK/onesignal/core/src/main/java/com/onesignal/core/internal/operations/impl
1 file changed
+20
-10
lines changedLines changed: 20 additions & 10 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
163 | 163 | | |
164 | 164 | | |
165 | 165 | | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
| 169 | + | |
| 170 | + | |
| 171 | + | |
| 172 | + | |
| 173 | + | |
| 174 | + | |
| 175 | + | |
166 | 176 | | |
167 | 177 | | |
168 | 178 | | |
169 | 179 | | |
170 | 180 | | |
171 | | - | |
172 | | - | |
173 | | - | |
174 | | - | |
| 181 | + | |
| 182 | + | |
| 183 | + | |
175 | 184 | | |
176 | | - | |
177 | | - | |
178 | | - | |
179 | | - | |
180 | | - | |
181 | | - | |
| 185 | + | |
| 186 | + | |
| 187 | + | |
| 188 | + | |
| 189 | + | |
| 190 | + | |
| 191 | + | |
182 | 192 | | |
183 | 193 | | |
184 | 194 | | |
| |||
0 commit comments