Hi
If you are calling back to the ui thread it should be on as long as you don't
try to update the same resource with two different methods / threads at the
same time. If you do lock{} the update and wait for the interface to refresh.
In my experience querying the same web service from multiple threads from
multiple clients results it the web service slowing to an almost crawl. Cache
as much as you can on the web service.
Davy
Sent from my iPhone
On 27 Apr 2016, at 09:49, Greg Keogh <[email protected]> wrote:
>> If you are not waiting for the tasks to finish, won't you run into a race
>> condition?
>
> The backend in my actual case is reading a web service, which can be hammered
> by overlapping calls. All of the callbacks will run on the UI thread, so they
> can't step on each other. I hope I'm right?! -- Greg
