om: Cezary Biernacki
Sent: lørdag 8. juni 2019 00:09
To: Tapestry users
Subject: Re: How to let the last ajaxResponseRenderer win?
Hi,
A server-side solution will not solve the problem, as responses from the server
can be re-ordered because of network transmission hick-ups. With Tapestry, yo
Hi,
A server-side solution will not solve the problem, as responses from the
server can be re-ordered because of network transmission hick-ups. With
Tapestry, you can the abort Ajax requests on client-side as well, it uses
Jquery (or Prototype.js) under the hood. I would monkey-patch
dom.ajaxRequ
Hi,
There’s no reliable way to do so as all requests arrive simultaneously on
the server side, so unless you do a distributed lock — which is not a good
idea usually — there’s no way to do so.
One of ideas is: you could pass sequential number with every request, put
that number in a storage (like
