Subject Effect of RemoteServiceName & RemoteServicePort on named pipes

Hi – I noticed behaviour that I found a little curious while playing around with named pipe connections using Firebird 3.0.3.


If you set RemoteServicePort to a non-default value, eg 3051, then the default service name is still used for named pipe connections, eg localhost@gds_db.


You can also set RemoteServiceName to the tcp port number and that will then be used for the named pipe, eg localhost@3051.  Is this a sensible way to provide consistent connection strings for tcp/ip and named pipe connections?





This e-mail message has been inspected for malicious content.

The information contained in this message and or attachments is intended only for the person
or entity to which it is addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the material from any system and
destroy any copies.
Please note that the views and opinions expressed in this message may be those of the
individual and not necessarily those of Foodstuffs South Island Ltd.

Thank you.