Hi Tom,
It sounds like you are doing too much in your heavy Ajax requests. You
should consider changing how it works so that the process can be started
by the Ajax request but does not need to block other ajax requests while
waiting for the results. You can use a progress bar to denote to the
user that something is happening and then once the work is done allow
them to access it (say through a link that is only visible when the
request is completed).
Others have mentioned the javascript client side checks but I like the
server side approach since all the context is already present to make
the decision on what to do with the Ajax call.
Regards,
Mike
I have a problem with my Wicket Application, which is quite Ajax heavy.
Certain ajax calls take some time as they start an import, however the
button can still be clicked and sends another ajax call (which is delayed
for quite some time). Is it possible to disable the button while the request
cycle is not complete? (I mean with wicket, or do I need to use
Javascript?). Also ajax calls are postponed as long as the channel is busy,
is it possible to deactivate this behaviour? And are there reasons why I
should not?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
