Re: [Firebird-devel] Connecting to Firebird on different ports: something is wrong.

[Dmitry Y. <di...@us...>]

Martijn,

> I'm surprised that I - apparently - am pretty much the only one
> that sees this as a problem. Is there anyone out there who thinks
> that the client should NOT read firebird.conf to find it's default
> port? (let alone, disable all others).
>
> I say: the client should use the port defined by "fb_db" in the
> "services" file, use 3050 by default, or use the connect string.
> That's it. That's all there is to it.

The connection string must override any other settings. Currently it's not
the case and this is a bug. I already have it fixed, but want to perform
some additional testing before committing.

As for the firebird.conf, there was an intention to use it on the client
side, to have all remote settings to be configured by default (for all
connections). But since both TCP/IP and NamedPipe ports can be specified in
the connection string, probably this idea isn't so useful. Okay, I see no
problems ignoring remote settings on the client side. But what about IPC
connections? If you change the memory map name (e.g. for compatibility with
IB6), you won't be able to connect locally from fbclient.dll. Should the
client IPC code use firebird.conf or not?


Dmitry