Subject | Re: [firebird-support] embedded twice |
---|---|
Author | Nando Dessena |
Post date | 2006-03-31T08:28:23Z |
Hello,
T> Having two applications using embedded to access a single database, is a
T> case of using the wrong tool for the job. In that case, a full server
T> should be installed, and all applications should use the regular client,
T> which is what it's designed for.
this is a perfectly respectable opinion, but it doesn't add any useful
element to the discussion. You basically say it should be done that
way because it should be done that way. I think there are several
other ways to do that, one of them would be a server embedded in a
separate application; another way is the classic shared model. In both
cases the advantages are a much lighter setup infrastructure and much
higher speed for embedded access.
Ciao
--
Nando Dessena
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================
T> Having two applications using embedded to access a single database, is a
T> case of using the wrong tool for the job. In that case, a full server
T> should be installed, and all applications should use the regular client,
T> which is what it's designed for.
this is a perfectly respectable opinion, but it doesn't add any useful
element to the discussion. You basically say it should be done that
way because it should be done that way. I think there are several
other ways to do that, one of them would be a server embedded in a
separate application; another way is the classic shared model. In both
cases the advantages are a much lighter setup infrastructure and much
higher speed for embedded access.
Ciao
--
Nando Dessena
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================