🚀 go-pugleaf

"Wiebe Vos" <wiebe@foxware.nl> wrote in message
news:46e7c1df$1@newsgroups.borland.com...

> The automationserver, once initially started from the main application,
> runs independend in the background and at certain intervals (via a timer)
> it launches the thirdparty program. This downloads a substantial amount
> of (stockmarket) data to a file, whose content is subsequently processed
> by the automationserver. After completion, the automationserver notifies
> the main application who takes further care of the data.

All the more reason you should be using asynchronous events.  Then there is
no blockage at all.  When the work is done, the server will tell the app
when it is ready.  The main application does not have to wait on anything.
This works especially well if the download is in its own thread that
notifies the server when the download is finished.  Then the download is not
blocking anything, not even the server that is doing the download.

> Anyhow the problem is solved by applying Bob Gonders suggestion.

Technically yes, but I would not recommend running a message queue from
inside the server itself.  It has no way of knowing what kind of app is
using it, what kind of messages to expect, whether those messages will cause
reentrant issues if processed at the wrong time, etc.


Gambit