From: Nando D. <na...@de...> - 2004-06-08 05:55:04
|
Alan, >> 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. A> but that's very rude isn't it? unlike a server which has a tendency to be A> left running all the time, a host application can be started and stopped A> frequently - my host application *is* a server and runs as a service. I'd think that anyone intending to embed (or otherwise implement) a server open to remote connections should take all the necessary precautions. Again, this is not specific to Firebird. In this context Firebird is just a component that I am using to build my server application. I would like that component to be in the form of a DLL rather than the current exe form. A> you wouldn't get me connecting to a host app with little chance A> of me being able to save my work before they decided to switch off and go A> home for the night.... ...which is also true for fbserver.exe running as an application. I hope what I wrote above clears the misunderstanding. Otherwise please feel free to repost. Ciao -- Nando Dessena mailto:na...@de... |