I'm sorry if this question is caused by my misconception of any kind. Also i've tried searching the forum, but didn't find anything useful.
As i can see, async calls from smartgwt components block user interaction with application.
As an example "fetch" operation on animals datasource in "build-in-ds" example can be executed through DMI with Thread.sleep() in it.
On fetch, the application hangs and waits for a response. Unfortunately, user has to wait too... He can't switch tabs (smartgwt tabs) and continue his work while waiting for the result.
This behavior is pretty disappointing if expencive fetch operations are performed.
Is this a problem or concept? And what are the best practices to overcome this.
As i can see, async calls from smartgwt components block user interaction with application.
As an example "fetch" operation on animals datasource in "build-in-ds" example can be executed through DMI with Thread.sleep() in it.
On fetch, the application hangs and waits for a response. Unfortunately, user has to wait too... He can't switch tabs (smartgwt tabs) and continue his work while waiting for the result.
This behavior is pretty disappointing if expencive fetch operations are performed.
Is this a problem or concept? And what are the best practices to overcome this.
Comment