|
From: Alex P. <pe...@in...> - 2005-10-10 15:51:03
|
Jim Starkey wrote: > That said, however, I don't think we want to retain WNet just for that > feature. I'm content to let the first machine that can legitimately > attach the database do so and let anyone else who tried to get an > error. I just want to make damn sure that they do get an error. > On the other hand, this feature is very convenient sometimes - user has network disk, and he want to open a database on that server. With automatic redirection enabled this works fine. I don't suggest to retain WNet for this feature. In fact automatic network redirection is not protocol-related feature, it is OS-related. In Unix we redirect NFS mounts, in windows - SMB mounts. TCP/IP may be easily used for this purposes with only one potential problem - when NetBIOS and DNS names of server do differ. But this means so badly administered network, that I suggest not to take into account such case. Ideal seems a case when single configuration parameter, something like AutomaticNetworkRedirection, affects both NFS and SMB, may be some more file sharing protocols in other OS's, up to being able to have plugins, implementing redirection for, for example, SAMBA on linux. In case when AutomaticNetworkRedirection is set to false, remote databases should be opened with exclusive lock. |