the_prashn
09-05-2007, 10:09 AM
This post is about my attempt to understand the Inner workings of a simple download manager, written in VC++.
Compared to a normal browser download, there appears to be two contrasting features, speed and resume capabilities.
If the file's host server is talking in HTTP (say it is Apache), will the client basically use the HTTP_RANGE to ask for chunks of a given file and run multiple threads downloading different portions of the file concurrently?
Similarly, when the exception is thrown, or when the download is deliberately paused, how exactly does it resume the download (by seeing the last byte received and the files total size)?
Are there any example VC++ projects to study this behavior from?
Compared to a normal browser download, there appears to be two contrasting features, speed and resume capabilities.
If the file's host server is talking in HTTP (say it is Apache), will the client basically use the HTTP_RANGE to ask for chunks of a given file and run multiple threads downloading different portions of the file concurrently?
Similarly, when the exception is thrown, or when the download is deliberately paused, how exactly does it resume the download (by seeing the last byte received and the files total size)?
Are there any example VC++ projects to study this behavior from?