06.04.2016 18:34, Dimitry Sibiryakov wrote:
>
> So, it is decided that Firebird 4 won't try to implicitly expand mounted
> network drives
> and UNC patches, right?
Correct.
Dmitry
--
Firebird-Devel mailing list, web i
06.04.2016 13:42, Dmitry Yemanov wrote:
> 06.04.2016 14:39, Dimitry Sibiryakov wrote:
>
>> 05.04.2016 17:46, Dmitry Yemanov wrote:
>>> I'd go even further and wipe out the named pipes (aka WNET) protocol
>>> too. I don't see any sense in it nowadays.
>>
>> But what to do with connections from old c
06.04.2016 14:39, Dimitry Sibiryakov wrote:
> 05.04.2016 17:46, Dmitry Yemanov wrote:
>> I'd go even further and wipe out the named pipes (aka WNET) protocol
>> too. I don't see any sense in it nowadays.
>
> But what to do with connections from old clients then?
They will be rejected due to lack
05.04.2016 17:46, Dmitry Yemanov wrote:
> I'd go even further and wipe out the named pipes (aka WNET) protocol
> too. I don't see any sense in it nowadays.
But what to do with connections from old clients then?
--
WBR, SD.
--
> 05.04.2016 18:24, Dimitry Sibiryakov wrote:
>>
>> In V4 will we still support connection to database on network share or
>> mapped drive
>> using the trick with overwriting "local" connection string to named pipes
>> one?
>> I.e. can expand_share_name() be cleaned out of isc_file.cpp?
>
> I'd g
05.04.2016 18:46, Dmitry Yemanov wrote:
> I'd go even further and wipe out the named pipes (aka WNET) protocol
> too. I don't see any sense in it nowadays.
+many
Vlad
--
Firebird-Devel mailing list, web interface at
h
05.04.2016 17:46, Dmitry Yemanov wrote:
> I'd go even further and wipe out the named pipes (aka WNET) protocol
> too. I don't see any sense in it nowadays.
It has one advantage over plain TCP: no tweaking of a firewall is required.
--
WBR, SD.
-
05.04.2016 18:24, Dimitry Sibiryakov wrote:
>
> In V4 will we still support connection to database on network share or mapped
> drive
> using the trick with overwriting "local" connection string to named pipes one?
> I.e. can expand_share_name() be cleaned out of isc_file.cpp?
I'd go even further
