Hi there,

I didn't see this previously asked anywhere: We want to use Firebird
embedded in our application, which runs on both Windows and Mac OS X,
but we would really like the firebird engine to run in a separate
process - for both stability, memory usage, and thread contention
issues (our app needs to keep as much out-of-process as possible).
We want to use the embedded client for its ease of distributing, and
the fact that these will be single-user databases.

As I understand it, the embedded build on Windows runs the Super
Server, and on the Mac, it runs Classic server; am I correct to
assume that on Windows, the embedded firebird engine is running in
the same process as the calling app, but on the Mac, it's in a
separate process? And if that's the case, would it be
straightforward to modify the Windows build to use the Classic server
model?

Thanks!

-Paul