On 23-4-2016 11:33, Helen Borrie helebor@... [firebird-support]
wrote:

> Hello Mark,
>
> Saturday, April 23, 2016, 6:02:00 PM, you wrote:
>
>> As far as I know even in Firebird 2.5 and earlier, settings like
>> ConnectionTimeout, TcpRemoteBufferSize and maybe some other settings
>> affected the client.
>
> But that is not to say that the client reads firebird.conf, is it?

fbclient.dll reads the firebird.conf (if it is in the some directory,
maybe on the path as well?). This is not (or not necessarily) the
firebird.conf in the Firebird server installation directory.

> Firebird.conf in all versions, including Fb 3, contains global
> settings, server-side, that affect all clients. The difference in Fb3
> is that some settings can be configured "per database" in
> databases.conf. Even those settings depend on what comes through the
> API. I suppose those client-side things could be configured in some
> kind of ini file but I've not heard of an API function that reads
> firebird.conf or databases.conf.

The client doesn't read the configuration through an API, it reads the
an actual firebird.conf if present (if none is found it applies the
default configuration).

The difference is that in Firebird 3 the configuration options in
firebird.conf can have more impact on the behavior of fbclient.dll than
it used to. As an example, if you modify the firebird.conf read by
fbclient.dll to have WireCrypt = Required, or if you remove Legacy_Auth
from the AuthCLient property, you will no longer be able to connect to
Firebird 2.5 or earlier.

> It's fair to say that few people know the Firebird API as well as you
> do. Are you saying that you have methods in Jaybird that read firebird.conf?

Jaybird itself doesn't, but if you use the Jaybird native, local or
embedded protocol, then the fbclient.dll loaded can and will read
firebird.conf if it is present.

Mark
--
Mark Rotteveel