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

Transfer Resume #52

Open
ypriverol opened this issue Jul 5, 2018 · 1 comment
Open

Transfer Resume #52

ypriverol opened this issue Jul 5, 2018 · 1 comment

Comments

@ypriverol
Copy link
Contributor

The transfer resume is important if the connection fails, we should be able to resume/restart the transfer.

@sureshhewabi
Copy link
Contributor

I checked this issue.

In Aspera, we are passing -k2 argument which means we have implemented the resume functionality(Aspera Resume). It is accurately working in the backend when you just pause the submission or when you close the tool and re-open. But in the front end, progress bar won't start where it resume in the second time when you try to continue.

In FTP, this resume functionality is not available. Unlike in Aspera, it wont check the last bytes and continue. The workaround I see is that we might have to update a temporary file(.px_tool/sub_record.px in the home folder) while data getting transferred/when application exits and then read read the last byte and reset the FTP start byte to the last byte. This is not straight forward solution which takes time. Need to find a better solution for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants