I haven't played with services very deeply, but if the sending
service first checks to see if the other service is alive before
sending the message, and it's not alive, then it can just wait for a
few seconds and check again.
From what I can find, QueryServiceStatus in the Windows SDK Help
might be what is appropriate to check whether the other service is
alive (but see the note under Remarks). This site might help also,
see the IsServiceRunning function:
http://coding.derkeiler.com/Archive/Delphi/borland.public.delphi.non-technical/2006-07/msg00594.html
At 12:13 AM 8/12/2009, J H wrote:
I have two applications running sending messages to each other.
Currently one of them crashes due to some memory violation, which I am
working on.
But as it terminates in a non normal way, it does not tell the other
app, that it is no longer servicing in-coming messages. Thus the other
app. hangs!
Is there a way for, say, a third app. or a separate thread to monitor
and service such hanging messages ?
As it is, I have to start both apps up from scratch. It would be very
unlikely the the window handle for the new edition of App 1 is the same.
And there is still that hanging message.
<P><p><font face="Arial, Helvetica, sans-serif" size="2"
style="font-size:13.5px">_______________________________________________________________<BR>http://www.sol.dk/
- debat mail horoskoper spil og meget mere</font>
_______________________________________________
Delphi mailing list -> Delphi@elists.org
http://lists.elists.org/cgi-bin/mailman/listinfo/delphi
Regards,
Sid Gudes
PIA Systems Corporation
sid.gu...@piasystems.com
_______________________________________________
Delphi mailing list -> Delphi@elists.org
http://lists.elists.org/cgi-bin/mailman/listinfo/delphi
