-
Notifications
You must be signed in to change notification settings - Fork 135
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
How does burst mode work for FTP? #98
Comments
This is how it works on the high level:
|
@bkueng Thanks! Is this correct then? A few assumptions (reasonable)?
|
Correct, looks good.
|
Thanks @bkueng
|
After the red arrow |
@bkueng That's why I am confused. At this point burst_complete=1. Are you saying that even after complete the server will send BurstReadFile? If so, I presume that it specifies size=0 and an empty data buffer. How many times? |
|
How does Burst ReadFile operations/streaming work?
I know that for normal reads, the file is read in chunks, with an ACK before each new chunk is sent. My guess is that for
BurstReadFile
the file is chunked and sent without waiting for a request - so basically you just send a stream of ACKs, with sequentially incremented sequence numbers. When you've sent everything you send the last ACK with the burst mode complete field set.The text was updated successfully, but these errors were encountered: