|
From: Leyne, S. <Se...@br...> - 2004-06-08 14:53:22
|
Nando, > G> Other than installation what other advantages would such a > G> configuration offer? >=20 > I think I have briefly said that in a post to Dmitry. Here it is: > synchronizing startup and shutdown of two processes, or more generally > maintaining a host/child relation between two processes is problematic > in Windows without introducing a third "guardian" application. Actually, if you investigate services further, you will find that you can define dependencies which will ensure that FB is started in order for your service to start (although the MS doc on dependencies is 'light'). Accordingly, starting your service will force Windows to ensure that FB is started, and closing FB will close your service. > Plus, fbserver.exe is shown > in the process list and could be terminated (since it runs as an > application) without my app noticing. But what about the remote connections? =20 You don't seem to be concerned about the impact of the start/stop of your application on their work. Not a good thing. > I could setup (partial) > workarounds for these situations, but I find the proposal I am > advocating simpler, more straightforward, more robust and in general > architecturally sounder. I wish I could agree with you...but I don't. Sean |