Hello,

> >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.

Against installing "normal" (full) server on Win98 machine:
- user could always shutdown server becouse he don't like Guardian or
server icon on system tray
- somebody could connect to such server throught TCP/IP

If Guardian or server icon could be hidden and server maintenance moved for
example into Control Panel (in Win98 of course , in WinNT/XP service is
almost perfect solution) and if there will be a solution to not allow others
to connect to server throught TCP/IP it will be sufficient for me (firewall
is not accepted solution due to troubles in configuration)

> 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.

Remote database is over very-very low bandwidth channel (modem connection)
, but the main problem are costs.

> >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.
>

Thank You.

>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>