并发Ajax请求限制为一个?-Wicket:concurrentAjaxrequestslimitedtoone?

9  

Yes, concurrent requests to a page instance are limited to one. Wicket Ajax will queue subsequent Ajax requests in the client side channel. See the wicket Ajax debugger for details in your running application.

是的，对页面实例的并发请求被限制为一个。Wicket Ajax将在客户端通道中对后续的Ajax请求进行排队。有关运行中的应用程序的详细信息，请参见wicket Ajax调试器。

This is done to make building your application easier: no need to work around concurrency issues on the server. Page access is always one done from one single thread: the current active request thread. If we didn't do this, we would have to synchronize on the component tree and make the whole programming model go yuk.

这样做是为了使构建应用程序更容易:不需要处理服务器上的并发问题。页面访问总是由一个线程完成:当前活动请求线程。如果我们不这样做，我们就必须在组件树上同步，并使整个编程模型运行良好。

4  

The problem was our AjaxIndicator which overlays a DIV over the entire page for the duration of each Ajax request. The "mouseup" (and consequently "click") events arrived when the overlay was in place, and thus lost. By holding the mouse button down and releasing it after the first Ajax request had completed and overlaying DIV removed, the second ajax request was fired.

这个问题是我们的AjaxIndicator，它在每个Ajax请求的持续时间中覆盖了整个页面的一个DIV。当覆盖层就位时，“mouseup”(并因此“click”)事件到达，因此丢失。通过按住鼠标按钮并在第一个Ajax请求完成并删除了DIV之后释放它，第二个Ajax请求被触发。

It seems obvious now as the whole reason why we have such an overlay is to prevent users clicking while an Ajax request is running.

现在很明显，我们有这样一个覆盖层的原因是为了防止用户在Ajax请求运行时点击。

I think my solution will be to disable the ajax indicator on certain, very quick requests such as these where it makes no sense to have an indicator (disregarding the potential that requests could take much longer in case of unusually high server load).

我认为我的解决方案将是在某些非常快速的请求上禁用ajax指示器(在服务器负载异常高的情况下，不考虑请求可能需要更长时间)。

0  

May be the response of the onblur ajax request may have error or the process you are performing after the ajax response may have error.

可能是onblur ajax请求的响应可能有错误，或者在ajax响应出现错误后正在执行的进程可能有错误。

If possible can you paste the code sniplet.

如果可能，您可以粘贴代码片段。