On Jan 31, 2008, at 7:47 AM, James Sentman wrote:
> Hi Dave The Threads Guy ;)
>
> But all networking events about new data still happen in the main
> thread right? And you have to hand that off to your thread for
> processing once you've read it? That is how you used to have to do it.
> But as you've noticed I am not up to speed on all the changes during
> my RB dark period ;) I never stopped using it, but we had children and
> the time I had to experiment with new things kind of disappeared...
>
> Thanks,
> James
James,
My app is fairly complex. As an example, the main window is basically
controlling
a Ham radio. It needs to stay very responsive to users input as well
as data from the radio.
While this is happening, I am receiving data via telnet, which may
need acting on.
So the telnet data is checked every second via a timer which starts a
thread to massage the data. From this data, as well as user entered
data, I need to fetch other info from the web via HTTP.Get. There are
two basic different sets of data. These are both performed in
threads. The delays in the data retrieval when implemented via
threads is the same as if done 'un-thraded', however, my main window
interface remains very responsive at all times. Before the threads,
the main window would basically stop while these other operations were
performed. So it works quite well, in my rather convoluted app ;-)
Dave
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|