Re: [Firebird-devel] WNet and XNet

[Alex P. <pe...@in...>]

Jim Starkey wrote:
> 
> OK, here is what I've heard:
>
>    * WNet is based on named pipes
>    * XNet is based on shared memory
>    * XNet is significantly faster than a local tcp connection
>
> I think we should consider phasing out WNet.  Microsoft itself have 
> dropped Netbui in favor on tcp.  It's on the WinXP/Pro kit as 
> unsupported and without a credible installation process.  There 
> certainly isn't any benefit to running WNet over tcp over running tcp 
> directly.  I don't see any problem with remapping WNet connect string 
> to tcp connect strings in the configuration files, so there shouldn't 
> be a compatibility issue other than networks with screwed up names.
>
> What are the ramifications of dropping WNet in Vulcan?
>

There is one more feature, impemented now using WNet. I mean automatic 
redirection of attachment to database, located on network disk. For 
example, after
net use t: \\srv1\shr1
attempt to open database t:\data\some.gdb will be redirected to server 
"srv1", which will translate file name in shared directory "shr1" 
(something like "\!shr1\!\data\some.gdb" is sent to the server) to local 
file name.
Certainly, there is absolutely no problem in using TCP/IP to connect to 
the server, not named pipes. But please take into account, that most of 
the code, performing detection of network drive on client and file name 
translation on server, is WNet related.

Alex.