Aage Johansen wrote:

>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 are right, I was not clear about that.
So far I have implemented firebird access for our applications using the
embedded version,
plainly because it doesn't have "something running continuously".
But as you point out, this will not allow several processes to share a
database.
I was aware of that, but wanted to verify first that we can use it at all
before I bother anyone with my special setup-problems :-)

>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.
>
>

Can I install/run/start/stop superserver without being root ?
From another thread in here I got the impression that this is not intended.
When you say "running it as an application", you are talking Windows, I
assume.
Can I have more then one instance on the same machine, serving on
different ports?
Would that require separate installations or can they run from the same
installation tree ?
Regards Thekla