Re: Possible collisions between Channels in wicket-ajax.js

it does, thnx, Martin Matej Knopp schrieb: Okay, i've fixed it. Thanks for pointing out the problem. Can you please confirm that the fix solves it for you? On 3/15/07, Martin Funk <[EMAIL PROTECTED]> wrote: Here ist is: https://issues.apache.org/jira/browse/WICKET-392 The chocking happens

Re: Possible collisions between Channels in wicket-ajax.js

Okay, i've fixed it. Thanks for pointing out the problem. Can you please confirm that the fix solves it for you? On 3/15/07, Martin Funk <[EMAIL PROTECTED]> wrote: Here ist is: https://issues.apache.org/jira/browse/WICKET-392 The chocking happens even on the same channel. Martin Matej Kno

Re: Possible collisions between Channels in wicket-ajax.js

Here ist is: https://issues.apache.org/jira/browse/WICKET-392 The chocking happens even on the same channel. Martin Matej Knopp schrieb: But the channel is only "dead" if the xmlhtprequest wasn't processed properly. And that should never happen. If the xmlhttprequest is in pol with readySt

Re: Possible collisions between Channels in wicket-ajax.js

But the channel is only "dead" if the xmlhtprequest wasn't processed properly. And that should never happen. If the xmlhttprequest is in pol with readyState == 4, then new xmlhttprequest should be created. Can you demonstrate the behavior you're describing on a quick start project? -Matej On 3/

Possible collisions between Channels in wicket-ajax.js

Hi, as I see it Wicket.Ajax.getTransport sometimes returns XMLHttpRequest objects that are in "readyState == 4" so they still might be processed by the "stateChangeCallback". Once "stateChangeCallback" reaches "t.onreadystatechange = Wicket.emptyFunction;" the freshly created XMLHttpReques