[
https://issues.apache.org/jira/browse/WICKET-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17043457#comment-17043457
]
Martin Tzvetanov Grigorov commented on WICKET-6750:
---------------------------------------------------
Yes, this will tell the XHR to close the connection from the client side. This
should stop uploading bytes for your use case of uploading huge file.
The server will find out that it is closed as soon as it tries to write
something back, i.e. at the end of the request cycle.
One issue I just realized: in your PR there was no logic to finalize the
processing, i.e. to call done(). This will remove the currently processed
channel and continue with the next scheduled one.
> add capability to cancel ongoing AJAX requests from client side
> ---------------------------------------------------------------
>
> Key: WICKET-6750
> URL: https://issues.apache.org/jira/browse/WICKET-6750
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-core
> Affects Versions: 8.7.0, 9.0.0-M4
> Reporter: Ernesto Reinaldo Barreiro
> Assignee: Ernesto Reinaldo Barreiro
> Priority: Major
> Fix For: 9.0.0-M5
>
>
> Currently it is not possible to stop an ongoing AJAX request form client
> side. This would be nice to have, on a per channel basis, for use cases such
> as:
> 1- user cancelling a long lasting AJAX upload or other not duration
> predictable AJAX requests?
> 2- add some logic at client side killing long running AJAX requests under
> certain conditions?
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
