Subject | Re: AW: [firebird-support] Embedded Firebird Libary using Firebird-Server |
---|---|
Author | Artur Anjos |
Post date | 2004-05-13T19:00:29Z |
Thomas von Stetten wrote:
have any problems deploying your application: just ask for the sysdba
password and you're ready to go.
That's what we get from easier deployment: people using Firebird as if
it was is own server.
But we should follow the rules, that could be as simple as:
1) Install the server if there is no server; change SYSDBA password at
install time and give that info to the user;
2) Use the server if there is one - ask for SYSDBA password.
For removing:
1) Remove your application;
2) Ask the user if he want's to remove the server part.
This way, we make live simpler as well for another applications.
We have a bad story with applications that 'register' the server and the
dtabases. Remember IBConsole? There's a lot of people that still asks on
support list how to register the server to be used by there own apps.
I don't think it's a good idea to have a global registy key for
applications to register. This will fail, soon or latter. And could also
compromise security.
computer. I doubt if they will remove yours, just stop using it. :-)
Our goal is to avoid situations like this. It's one more point for you
against competition: you let the user know what they have. :-)
Artur
> HI Artur,If everyone follow the rules for client/server deployment, you shouldn't
>
>
>>How do you think that people that deploy Oracle or Microsoft SQL
>>applications do? Give a message to the user asking 'do you want me to
>>remove Oracle since I don't use it anymore?'
>
> That's one of the reasons I decided to use Interbase (and later Firebird).
> It's easier to deploy - I thought. If I had the chance I would switch to a
> desktop database. Most of my problems/error come from the fb-server
> installation/concurrency with other installations.
have any problems deploying your application: just ask for the sysdba
password and you're ready to go.
That's what we get from easier deployment: people using Firebird as if
it was is own server.
But we should follow the rules, that could be as simple as:
1) Install the server if there is no server; change SYSDBA password at
install time and give that info to the user;
2) Use the server if there is one - ask for SYSDBA password.
For removing:
1) Remove your application;
2) Ask the user if he want's to remove the server part.
This way, we make live simpler as well for another applications.
We have a bad story with applications that 'register' the server and the
dtabases. Remember IBConsole? There's a lot of people that still asks on
support list how to register the server to be used by there own apps.
I don't think it's a good idea to have a global registy key for
applications to register. This will fail, soon or latter. And could also
compromise security.
> As I explaned/showed before the main problems are the non-dedicated servers.Let it be. Firebird is so small that it will not hurt any hard disk space.
> We are talking about small - very small - companies. They don't havePeople like this are used to have a lot of software installed in there
> it-professionals. And they are real dummies regarding to computers. They do
> not know what a server is. So I can't expect them to know about a DB-Server!
computer. I doubt if they will remove yours, just stop using it. :-)
> My competitors also don't. The other problem is that the other applicationsThat's no example to follow. Bad applications are all over the place.
> don't tell them that they use a DB-Server they simply install
> Firebird/Interbase - that's it. So how can they know that/if they use a
> firebird-server or not.
Our goal is to avoid situations like this. It's one more point for you
against competition: you let the user know what they have. :-)
Artur