Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improved implementation for FutureTransfer.listenFor #35

Merged
merged 1 commit into from
Apr 22, 2015

Conversation

dwhjames
Copy link
Owner

Cast to internal type AbstractTransfer so that a
low-level state change listener can be attached.
In light of issue #30, this provides a more foolproof
implementation of listening to transfer events.
There is now a three-way race to complete the
promise that signals the completion/termination of
the transfer.

This adds an integration test for s3, using the
fakes3 ruby gem.

closes #30

Cast to internal type `AbstractTransfer` so that a
low-level state change listener can be attached.
In light of issue #30, this provides a more foolproof
implementation of listening to transfer events.
There is now a three-way race to complete the
promise that signals the completion/termination of
the transfer.

This adds an integration test for s3, using the
fakes3 ruby gem.

closes #30
dwhjames added a commit that referenced this pull request Apr 22, 2015
Improved implementation for FutureTransfer.listenFor
@dwhjames dwhjames merged commit a135f03 into master Apr 22, 2015
@dwhjames dwhjames deleted the topic/s3-state-change branch April 22, 2015 01:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

FutureManager hangs indefinitely in the case of a bad file.
1 participant