Thekla Damaschke wrote:

> ...
> I have implemented the access layer against firebird (using embedded as
> starting point)
> and it was really smooth. Great !
> But now, to set it live, I need some help on the alternatives:
>
> If I got it right, superserver needs something running continuously
> on each machine I want a distributed database to end up on,
> while classic server should be integrated with inetd and will start up
> on request (one process per database connection).

I haven't used embedded, but I think that for "embedded" there is no
"something running continuously". For "ordinary Superserver" there
is a process running.

You also wrote:
<<An evaluation job will consist of several processes that interact
and work against the same database>>

If these evalauation jobs will run _simultaneously_ you should use
standard SuperServer (embedded will not allow this).
The footprint of SuperServer is quite small, and just having it
running would probably not be a problem for any computer - about 8MB
for fbguardian and fbserver combined. You can stop them if and when
you want to. Or start fbserver as application as needed.

> Both of them should cope with new databases turning up on the fly
> and shouldn't care if a database vanishes once it is not longer
> accessed, right ?
> ...

Right.


Note that I've only used Superserver (as a service), so someone will
probably correct and amend the above.


--
Aage J.