Page 2 of 2
Re: NRDS "buffer" to send results once connection restored
Posted: Wed Jan 27, 2016 6:42 pm
by derekb
tmcdonald wrote:This would need to be discussed. I'm somewhat on the fence as to whether this should be default, though I do lean slight to the "yes" side. I could see cases where someone would not want disks to fill up because they have network issues all the time, or they have restrictions on saving this sort of thing, but those would not be the majority.
I think if anything, enable by default and publish in the docs how to disable if desired.
Re: NRDS "buffer" to send results once connection restored
Posted: Thu Jan 28, 2016 2:56 pm
by tgriep
That is a good idea about the documentation.
Did you try the fix and did it work for you?
Re: NRDS "buffer" to send results once connection restored
Posted: Thu Jan 28, 2016 2:57 pm
by scottwilkerson
derekb wrote:tmcdonald wrote:This would need to be discussed. I'm somewhat on the fence as to whether this should be default, though I do lean slight to the "yes" side. I could see cases where someone would not want disks to fill up because they have network issues all the time, or they have restrictions on saving this sort of thing, but those would not be the majority.
I think if anything, enable by default and publish in the docs how to disable if desired.
I'm going to suggest it goes the other direction, disabled by default, but options to turn it on..
Here's my reasoning behind this.. NRDS get installed on clients, and in theory, with a mis-configuration you could fill a client disk with the generated XML, causing catastrophe. Therefore, you should have to deliberately turn the feature on.