|
From: Jason D. <ja...@bb...> - 2005-10-03 15:19:12
|
WNet is a layer on top of NetBIOS, not NetBEUI. NetBIOS is now a bound service on TCP/IP in Windows >= 2000. Jason 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. > > 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? > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > Firebird-Devel mailing list, web interface at > https://lists.sourceforge.net/lists/listinfo/firebird-devel > > |