J
JimTheAverage
I am writing an app that checks web pages for data for clients
automatically. In order to keep the interface from locking up during
intense loops, I was considering using backgroundworker objects.
While using a single backgroundworker object is simple enough, it is
not fast enough. And, looking at the code needed to raise progress
events and completion events, I was wondering if there was a method to
create an array of a single backgroundworker class and have them all
working (retrieving data and sorting it) without having them bump into
one another.
My thought was of a master backgroundworker that would launch and
manage several other background workers. This seems a bit complex
though, and I was wondering if anyone had tried this, has seen
examples of this or had any thoughts that may help me in this pursuit.
Thank you for your help.
automatically. In order to keep the interface from locking up during
intense loops, I was considering using backgroundworker objects.
While using a single backgroundworker object is simple enough, it is
not fast enough. And, looking at the code needed to raise progress
events and completion events, I was wondering if there was a method to
create an array of a single backgroundworker class and have them all
working (retrieving data and sorting it) without having them bump into
one another.
My thought was of a master backgroundworker that would launch and
manage several other background workers. This seems a bit complex
though, and I was wondering if anyone had tried this, has seen
examples of this or had any thoughts that may help me in this pursuit.
Thank you for your help.