[
https://issues.apache.org/jira/browse/CB-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723846#comment-13723846
]
Christoph Kappel commented on CB-1863:
--------------------------------------
I don't think that the issue is fixed, the example is mildly saying completely
pointless. It suggests to pass the same success/error callback to
FileTransfer#abort and there's no explanation what is to be expected there.
Does success mean the abort was a success? What situations can occur, that
abort calls the error callback?
Also the example contains bytes sent stuff in the success callback, so on
success FileTransfer#abort returns how many bytes were send? If so, what is the
point of that, since Cordova usually pre-writes the size of the file to
storage. The information would be nice, if a transfer is resumeable, but I
don't think that is the case in the current state.
> FileTransfer.abort needs a quick example
> ----------------------------------------
>
> Key: CB-1863
> URL: https://issues.apache.org/jira/browse/CB-1863
> Project: Apache Cordova
> Issue Type: Task
> Components: Docs
> Reporter: Shazron Abdullah
> Assignee: Shazron Abdullah
> Fix For: 2.4.0
>
>
> The abort function takes two params: a success and error callback.
> https://github.com/apache/incubator-cordova-js/blob/master/lib/common/plugin/FileTransfer.js#L145
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
