Very nice so,
1) create a "master app"
1a) User Master App's cooperative threads to launch Slave/Helper apps.
2) create "slave/helper apps"
3) communicate between master and slave/helper via ipcsockets.
3a) Use a "are you alive" pinging method between master and slave.
Giovanni
----------------------
Tim Jones wrote:
> On May 30, 2008, at 10:19 AM, Giovanni wrote:
>
>
>> But even on a single processor, you would see a tremendous gain if
>> the required process is doing stuff like a downloader helper app.
>> The helper app would continue to download while the master app would
>> remain highly responsive. Would that be right?
>>
>
> So long as the UI is properly set to handle the external process.
> This is why I use RB's cooperative threads when I kick off the helper
> tool. Just executing the external process can actually cause the UI
> to become non-responsive if the management / monitoring the external
> process isn't coded properly.
>
> Tim
>
> _______________________________________________
> Unsubscribe or switch delivery mode:
> <http://www.realsoftware.com/support/listmanager/>
>
> Search the archives:
> <http://support.realsoftware.com/listarchives/lists.html>
>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|