I'm not sure that a second request needs to wait for the first to
complete (serialization). You could timestamp requests coming in, then
ignore responses with outdated timestamps on the client. For some
applications that would be more responsive.


Igor Vaynberg wrote:
> we dont have support for serializing ajax requests yet, its been on my
> todo list for quiete a while but lately i just havent had much available
> time. please add an rfe for it.
> as far as the different throttle behavior i think thats a bit out of our
> scope. if you want something like that you can implement it yourself.
> -Igor
> On 7/14/06, *Nathan Hamblen* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>     What are people doing to make sure their ajax responses apply to pages
>     in the correct order? I'm using an onkeyup form component updater for a
>     find-as-you-type query a fairly large database. Incorrect results are
>     often rendered because the second-to-last request responds after the
>     actual last request. (This makes sense, as a query returning fewer
>     results is often faster.)
>     It's a "like '%token%'" query so mysql has to scan the whole table.
>     Bummer, but I need that first %. I played around with the throttle delay
>     but it didn't make a difference. I'd like to just throw out the
>     out-of-order response. Even better would be if the ajax request didn't
>     happen until the user paused typing.
>     Any ideas?
>     Nathan

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
Wicket-user mailing list

Reply via email to