Subject | Firebird 1.5 as a different service name |
---|---|
Author | Jonathan Hull |
Post date | 2004-05-18T03:51:53Z |
Hi all,
I would like to have my cake and eat it too, in that I would like my
application to use a Firebird 1.5 service on an alternate port for my
exclusive use, while not conflicting with a different Firebird 1.5
service to exist on the standard 3050.
Ideally I would envisage a situation similar to Apache, where the
service name can be supplied as a parameter to the executable on
execution.
Does anyone know if there are any architectural reasons why this
can't happen, or if this is possible, or if with a simple bit of code
change it could be achieved? It would most definitely save me the
concern of whether a Firebird is installed, and what version etc.
Cheers,
Jono
I would like to have my cake and eat it too, in that I would like my
application to use a Firebird 1.5 service on an alternate port for my
exclusive use, while not conflicting with a different Firebird 1.5
service to exist on the standard 3050.
Ideally I would envisage a situation similar to Apache, where the
service name can be supplied as a parameter to the executable on
execution.
Does anyone know if there are any architectural reasons why this
can't happen, or if this is possible, or if with a simple bit of code
change it could be achieved? It would most definitely save me the
concern of whether a Firebird is installed, and what version etc.
Cheers,
Jono