You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 16, 2018. It is now read-only.
From my understanding if I call cancel on a LRRestyRequest it stops the NSURLConnection and calls finish, which in turn calls the completion block. However there is no way of knowing in my completion block that the request actually got canceled.
I would think that when canceling a long GET or POST operation the completion block either:
should not be called (after all we explicitly force a cancel)
should be called but it should have a way of doing that it is called because of a cancel and not because of a finish
What do you think?
The text was updated successfully, but these errors were encountered:
From my understanding if I call cancel on a LRRestyRequest it stops the NSURLConnection and calls finish, which in turn calls the completion block. However there is no way of knowing in my completion block that the request actually got canceled.
I would think that when canceling a long GET or POST operation the completion block either:
What do you think?
The text was updated successfully, but these errors were encountered: