You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current implementation uses Executor, which makes it harder to perform scheduled tasks or to perform task chaining. Currently tasks are enqueued by invoking a static method:
returnTask.call(newCallable<Void>() {
publicVoidcall() throwsException {
// ... do the work ...returnnull;
}
}, taskExecutor);
Typical Parse code is written using TaskQueue instead:
returntaskQueue.enqueue(newContinuation<Void, Task<Void>>() {
@OverridepublicTask<Void> then(Task<Void> toAwait) throwsException {
returntoAwait.continueWithTask(newContinuation<Void, Task<Void>>() {
@OverridepublicTask<Void> then(Task<Void> task) throwsException {
// ... do the work ...return <ataskthatresolves when theworkiscomplete>;
}
});
}
});
The end result is largely the same, but using TaskQueue will help keep the architecture more in line with what is already established in Parse-SDK-Android.
The text was updated successfully, but these errors were encountered:
Sorry it was my first time using that Framework when I made the initial project. I tried to do the same as how it's done in the existing parse platform.
Thanks, and I'll learn about it :)
Current implementation uses Executor, which makes it harder to perform scheduled tasks or to perform task chaining. Currently tasks are enqueued by invoking a static method:
Typical Parse code is written using TaskQueue instead:
The end result is largely the same, but using TaskQueue will help keep the architecture more in line with what is already established in Parse-SDK-Android.
The text was updated successfully, but these errors were encountered: