Is it a bug in the JQuery xhr.abort() then? Debugging RequestFilter.service
I found that request.request.request._connection._parser._state = -13 (
org.mortbay.jetty.HttpParser.STATE_START) when things goes wrong (Should be
org.mortbay.jetty.HttpParser.STATE_CONTENT). I did not figure out how I can
test on this value, so I change my JavaScript code:
owner.simplifyPolylineLastCallCnt = 0;
owner.simplifyPolyline = function (tolerance) {
owner.simplifyPolylineLastCallCnt++;
var callId = owner.simplifyPolylineLastCallCnt;
$.post("/map/client/trackdraw:DouglasPeuckerSimplifier", {
}).done(function (data) {
if (callId != owner.simplifyPolylineLastCallCnt) return;
// DO THE WORK
Now I can set onDouglasPeuckerSimplifier back to allowBlank = false and
skip the == null test :-)
Forgot to tell that I am running Tapestry 5.4-beta-26.
*From:* Lance Java [via Apache Tapestry Mailing List Archives] [mailto:
ml-node+s1045711n5730599...@n5.nabble.com]
*Sent:* 7. mai 2015 11:39
*To:* Svein
*Subject:* Re: Detect jqXHR.abort()
The server will know about an aborted request as it's too late, the request
has already been sent. Abort is a clientside concept AFAIK which stops the
client from waiting for the response / processing it.
------------------------------
*If you reply to this email, your message will be added to the discussion
below:*
http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/Detect-jqXHR-abort-tp5730595p5730599.html
To unsubscribe from Apache Tapestry Mailing List Archives, click here
<http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2375124&code=c3ZlaW5AamFjaWxsYS5ub3wyMzc1MTI0fC0xNTM4NzY2ODg4>
.
NAML
<http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
