I've designed and built at least two systems like that and neither used or needed multi-threading.

I agree with the earlier comment (I think from Scott) that you invariably end up with so much infrastructure to avoid screwing up that any potential advantages are lost. Maybe in real-time control systems or indeed operating systems it would be worth the effort - but not in applications programming when there are simple alternatives.

Jon Paris


On 4-Sep-09, at 6:03 PM, midrange-l-request@xxxxxxxxxxxx wrote:

If the interactive subsystem was designed along the lines of an event
driven framework there would be a real need for threads. Where the
keypress of any of the AID keys was handled by signaling an event in
the RPG program. The event handlers are required to not do much work
so that the main program loop could continue to read from the event
message queue. Long running functions like F7 to scan a document or F8
to get data from a web service would run in a thread and signal an
event when done.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].