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

filetransfer only transfers 1 file until finished or paused (not round robin over all pending FTs) #763

Closed
zoff99 opened this issue Feb 5, 2018 · 7 comments
Labels
bug Bug fix for the user, not a fix to a build script messenger Messenger P3 Low priority
Milestone

Comments

@zoff99
Copy link

zoff99 commented Feb 5, 2018

while (ft->status == FILESTATUS_TRANSFERRING && (ft->paused == FILE_PAUSE_NOT)) {

@iphydf i think we need to change this while loop. can you help me here a little bit?

@sudden6
Copy link

sudden6 commented Feb 6, 2018

personally I'd prefer to have one finished file instead of a bunch of half finished stuff if the chat contact goes offline. Why do you want to change this behavior?

@zoff99
Copy link
Author

zoff99 commented Feb 6, 2018

because now toxcore choses a random FT and finishes that. this FT maybe a very large file.
and other smaller (png, jpeg) will be blocked until this is finished.

i consider this a bug, rather than a feature.
the user should decide how many FTs he will start, not toxcore.

@tox-user
Copy link
Member

tox-user commented Feb 6, 2018

I think it's always better to have one whole file than many broken parts that you can't use. If you get disconnected during a file transfer you will only have to resend that one file, which means less bandwidth wasted and increased chances of receiving a file when you are on a poor connection. If the user is sending multiple files, they should be sent one by one in order and not randomly.

@anthonybilinski
Copy link

The case zoff99 mentioned is convincing. If you're transferring a huge file to a friend that takes 20 minutes and are chatting at the same time, being able to also send small images that you're chatting about would be nice. Users can already manually accept files or pause if they want to focus the download, and clients could implement queueing of "large" files if wanted, but still allow "small" files or files of certain types to go at the same time.

@sudden6
Copy link

sudden6 commented Feb 8, 2018

with the very large file it makes sense 👍

@zoff99 zoff99 added bug Bug fix for the user, not a fix to a build script messenger Messenger labels Feb 13, 2018
iphydf pushed a commit to zoff99/c-toxcore that referenced this issue Feb 17, 2018
Instead of 1 FT blocking all others while it is active.

Fixes TokTok#763.
@zoff99
Copy link
Author

zoff99 commented Jul 3, 2018

@iphydf @robinlinden isn't this merged already?

@iphydf
Copy link
Member

iphydf commented Jul 3, 2018

Yes that's done by you.

@iphydf iphydf closed this as completed Jul 3, 2018
@robinlinden robinlinden modified the milestone: v0.2.11 Mar 20, 2020
@iphydf iphydf added this to the meta milestone Feb 4, 2022
@iphydf iphydf added the P3 Low priority label Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug fix for the user, not a fix to a build script messenger Messenger P3 Low priority
Projects
None yet
Development

No branches or pull requests

6 participants