Subject | Re: [IBO] IB_Connection and port of server |
---|---|
Author | Helen Borrie |
Post date | 2003-09-04T02:43:59Z |
At 11:08 AM 3/09/2003 -0700, you wrote:
in the client's Services file. OK, there are really two parts to this answer:
1) The Firebird client doesn't need a Services file entry at all if the
server is broadcasting from port 3050. So you need to configure the
**server** explicitly to broadcast from a different port (that's in
firebird.conf). There are other platform-specific ways, but the conf file
setting works for all platforms.
2) On the client, you have two ways to tell the client to listen on a
different port. One is to include the port number in the connection
string. This is OK but not great, because you have to do it for each
application. If you configure it in the client's Services file, it works
for any application being run from that client.
Don't apply these assumptions to InterBase. It remains as it always was.
Helen
> > A better way is to set up the port as default in firebird.conf on theGood question, it won't, unless you also set up the explicit gds_db entry
> > server, so applications don't have to worry about it.
>
>How would the client be aware of something in the server config file?
in the client's Services file. OK, there are really two parts to this answer:
1) The Firebird client doesn't need a Services file entry at all if the
server is broadcasting from port 3050. So you need to configure the
**server** explicitly to broadcast from a different port (that's in
firebird.conf). There are other platform-specific ways, but the conf file
setting works for all platforms.
2) On the client, you have two ways to tell the client to listen on a
different port. One is to include the port number in the connection
string. This is OK but not great, because you have to do it for each
application. If you configure it in the client's Services file, it works
for any application being run from that client.
Don't apply these assumptions to InterBase. It remains as it always was.
Helen