> ND> I don't buy the argument that Firebird is less prone to crashes and
> ND> memory overwrites than my own application, just because it is
> ND> Firebird. If I decide to host database engine threads in my own
> ND> process space I should know what I am doing, of course, but I wouldn't
> ND> rule out the option beforehand.
>
> My point is that _if_ your app goes mad, it can get the embedded server
> to do dirty things to the database. And the reverse too : if the
> firebird embedded server goes mad, it can have adverse effects on your
> hosting app. Running both in their individual space, does not make any
> of them better. It is just that they can't collaborate to bring chaos.
>

Olivier,
Do you have any evidence of this? What sort of "goes mad" behaviour are you
talking about.
You have now scared off at least one person from using the embedded server.
But I'm very interested to hear more detail on this. Or is this claim based
solely on the theory that executables which dynamically load dll's can make
those dll's do strange things? And which theory is this?
Alan