Re: [Firebird-devel] WNet and XNet

[Jim S. <ja...@ne...>]

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.

Truth be told, I'm not wild about XNet, either -- memory shared between 
client and server gives the clients too many opportunities to crash the 
server for my taste, but I'm not prepared to argue against the 
performance numbers.  And again, if there is a problem, a user could 
tweak the configuration files to redirect local connections through tcp 
to localhost.

What are the ramifications of dropping WNet in Vulcan?