You can have the initial RPC request kick off a sub-process (new
thread, pass a message to another process, etc..) and then return some
sort of id to your client that uniquely identifies the particular
process the user initiated. The client can then emulate the blocking
w/ a dialog or something
Does really no one got any idea?
On 29 Nov., 18:29, newnoise tommmuel...@googlemail.com wrote:
Me again,
just tried to make the imExpensive-method less complex, but still no
success.
TheRequestis not cancelled ... What am I doing wrong?
Thanks
Tom
On Nov 29, 6:16 pm, newnoise
All calling it does is call the abort() method of XmlHttpRequest which
will stop the execution of your callback, it doesn't do anything on
your server.
Check the Request.cancel() code..it's pretty straightforward.
On Dec 7, 7:01 am, newnoise tommmuel...@googlemail.com wrote:
Does really no one
Ok. Too bad ...
Is there any way to abort the running method on my server?
Thanks
Tom
On 7 Dez., 16:54, jhulford jhulf...@gmail.com wrote:
All calling it does is call the abort() method of XmlHttpRequest which
will stop the execution of your callback, it doesn't do anything on
your server.
Hi,
I'm working on an GWT-App displaying a map with different layers.
Some of those layers are drawn just on request and just for the part
of the map which is currently displayed.
The Problem occurs if a user moves and zooms the map pretty fast, so
that a lot of pictures have to be drawn. This
Me again,
just tried to make the imExpensive-method less complex, but still no
success.
The Request is not cancelled ... What am I doing wrong?
Thanks
Tom
On Nov 29, 6:16 pm, newnoise tommmuel...@googlemail.com wrote:
Hi,
I'm working on an GWT-App displaying a map with different layers.
