The WebRequestCyclyProcessor substitutes without warnings or error messages ajax requests, when wicket is at the same time processing page requests for that page. This may break applications that serve non-shared resources such as images (which will also trigger erquests to the page), and do ajax requests from the same page. Afaik, as a programmer you have no control over when the browser actually makes requests for the images on the page, and how long these requests take. But during such requests all ajax processing of the page is silently ignored.
Can somebody shed some light on why this is actually implemented this way, and if I am correct considering this is a bug?
