On 6 May 2003 at 17:37, Bogus aw Brandys wrote:

>I want to ask how to implement such situation (I think common):

I think else. :)

>I have an application which connects to remote Firebird database
>server when possible and do some updates and also read some data to be
>stored in local database (which is simple a mirror of remote). I'd
>like to use fbembeded to avoid installing full server on client
>machine (Win98) , but fbembed.dll seems to be only server engine
>without client , and I can't use it as replacement for gds32.dll

This was discussed in firebird-devel some time ago and I was one
who voted against client code in embedded engine.

>(client library) for remote connections. So, I must load different
>library each time I connect to local or remote database, Am I right ?

So far yes. Could you provide more strong reasons against
installing "normal" server on a client computer? If somebody can
manage to install FB in one place (remote machine), the person can do
it for other computers (client machines). FB is easy to install and
doesn't need hard maintenance for small DBs.
As long as the engine cannot do heterogeneous queries, partial
local mirror seems to be useless. Local cache for individual tables
can be made by much lighter engines (including in-memory tables and
text files). Well-designed client application doesn't abuse network
wire and even 10Mb coax is more than enough.
If we are talking about the case when remote database is over low-
bandwidth channel... I'd recommend full (or application-depended
partial) replication to local workgroup server.

>This is very confusing and make troubles.Could fbembed.dll contain
>also client library ?

Could. But I don't think that must. A couple days back someone
called libfbembed.so "a client library"... Weirdy.

SY, Dimitry Sibiryakov.