Closed LukaszByczynski closed 8 years ago
So what sort of exceptions these would be? But yeah, currently client side will not ask multiple times. Best way to provide new UI content would be to do it async. Just start thread to query data, and then add components with runnable given to UI.access. This way if you DB query throws exceptions, you can wait some time and retry. If you DB fails multiple times, then you can put error label to layout and ask it to stop asking new content (removes loading indicator).
Closing as unresolved issue.
I wonder, how abort loading process when something goes wrong in Lazy ComponentProvider? Currently, after exception load indicator doesn't change UI state. Is it possible to abort loading process, and wait until user tries scroll next time?