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

[Martijn T. <m.t...@up...>]

Hi,

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.

--
Martijn

> > > Well, that might be great and all... but then how are you supposed to
> > > connect to a remote server on a different port then, if fbclient is
> > > forcing itself to the port defined for your local firebird server?
> >
> > I tend to agree it becomes tricky...
> 
> "tricky" ... How about "nearly impossible". Really, as a Firebird user
> and developer that uses multiple instances, I have no idea why the
> client is forcing itself to use a non-default port (that is, without
> defining
> the port in the "services" file).
> 
> > > And
> > > why is this "as designed"? I've changed "firebird.conf", this is a
> > > server config file, right?
> >
> > It's also a client config file. And always was. Even in FB1 some config
> > options are client-only.
> 
> And before Fb1?
> 
> --
> Martijn