|
From: Alan M. <al...@me...> - 2004-06-08 05:45:11
|
> A> If the application hosting the dll desided to quit, what would > happen to 3rd > A> party applications using the dll as it's means of serving > data? The host > A> application would just close and drop the dll wouldn't it? > > Yes. Much like what happens when you shutdown an application that > hosts an embedded server (fbembed.dll) or the fbserver itself. Client > connections vanish. but that's very rude isn't it? unlike a server which has a tendency to be left running all the time, a host application can be started and stopped frequently - you wouldn't get me connecting to a host app with little chance of me being able to save my work before they decided to switch off and go home for the night.... > > For graceful shutdown a stop() exported function that pairs the > start() one would be useful, but anyway Firebird is able to > suffer termination without corrupting the data (in forced writes mode, > that is). > > Ciao > -- > Nando Dessena That shoutdown would be fine if it were being called from the third party application but if the host application called it, you would need a mechanism to warn the 3rd party app to get ready for shutdown. Alan |