user interface - Progress bar requirement as sufficient justification for multithreading via BackgroundWorker? -
Given that multi-threaded applications are debunking hell and should be avoided at all cost ...
Is there a sufficient reason for registering a progress bar to enter multi-threaded land?
Specifically, assume that C # windows forms .NET 3.0 application requires downloading 100 MB file. Is it right to download multi threads (via a background variant) to download it on a thread, so that UI progresses to the progress bar showing progress in the thread?
Sorry if this question is a bit fuzzy. I have not multi-threaded anything before.
You have not said anything about which language you are using; For example, you can use WebClient
with DownloadFileAsync
and DownloadProgressChanged
While this is a multi-threaded program, I consider this as a less complexity program.
Comments
Post a Comment