|
From: Jason D. <ja...@bb...> - 2005-10-03 19:46:36
|
I am not sure where the confusion came in, but WNet is a far from dropped technology from MS. This is how you enum computers in your workgroup, join a domain, and all of the other super goodness windows networking supplies. Of course, I cant see any perticular reason that firebird would use it explicitly... but if it does, I think you will be hard strapped to find an alternative for a lot of the functionality (an yes, even .NET is dependent on it). Jason Jim Starkey wrote: > Dmitry Yemanov wrote: > >> "Jim Starkey" <ja...@ne...> wrote: >> >> >>> What are the ramifications of dropping WNet in Vulcan? >>> >> >> >> I would prefer WNet to be kept, just to provide people with some choice. >> >> >> >> > Could you explain why? It seems to me that reducing the size and > complexity of the project by dropping an obsolete component using an > obsolete protocol created and dropped by Microsoft would make a lot of > sense, particularly since the change can be made transparent, at least > on systems configured for TCP/IP. Choice is well and good, but if the > choice is always the wrong answer, do it really make sense to offer it > as an alternative? > |