Re: [Firebird-devel] Embedded superserver

[Olivier M. <om...@ti...>]

Nando Dessena wrote:

> I don't want the firebird server to be available for anyone to stop it
> or even see it. I don't want anyone perceiving that something called
> "firebird" exist on the machine, except from the "powered by firebird"
> logo in my application's about box. I want to run (as an application)
> on machines that don't support services (Win98). I want to be able to
> seamlessly install on machines which already have IB and/or Fb
> installed and running, without causing harm to them. Plus I want all
> the other things that I have already explained, of which the ability
> to ensure that Fb get woken up when my service starts is but the tip
> of the iceberg.
> 
> If anyone can come up with a different solution that allows all this
> I'd be happy to hear.

I use FB SS executable as compiled and provided by the Project download 
area (no private build). The setup of the end-user application installs 
bits of a typical FB SS distribution to one of the application folders. 
Setting up a NT service for the SS (if services available). The end-user 
application while starting up, takes care to start that FB copy as an 
application if not configured as a service or checks that FB service 
runs and starts it. Guardian is not shipped/used. The end-user 
application does the pampering. Of course config files shipped use 
different tcp/ip ports than standards and some other settings so that 
this "private" copy of FB on any machine does not conflict with any 
other one. I can install to a server without having to care wether 
another FB or IB is already installed other there. Nothing is copied to 
System directories. The end-user application knows where to find local 
client DLL. And knows where to find private copies of tools needed.

That's as close as I can get to your requirements without touching a 
single line of code of FB, be it engine code, server code or even its 
build procedures.

Might help you as a not_that_bad alternative.

[ This is all on Windows. I suppose similar configuration efforts should 
be possible on Linux. I used to know those systems but named them Unix 
by that time. ;-) ]

-- 
Olivier Mascia