Bogusław Brandys wrote:

>>
>>adding the TCP server code to fbembed, together with an API to start
>>and stop listening would be enough. Then one application in the group will
>>host the server & database engine for the others to use. Me and others
>>have been asking for this supposedly trivial feature many times in the
>>past, but the general objection has always been along the lines of:
>
>
> Nice.Could it be however even simpler.For example just a mutex check
> inside fbembed.dll on first DLL loading and one function to set this
> mode and mutex name ? Second ,third and other fbembed.dll load call will
> function (in this mode) just like a local client code only.
> Only the first fbembed.dll load will create superserver embedded engine.
>

Yes it's possible - after all, it's only code and infinitely malleable,
however what you're talking about is not a DLL. It would be yet another
"architecture" for Firebird. Anybody who says that's trivial doesn't
understand the problem.


Regards,


Ann