PF
You have the proxy initiate the connection then, and the logic to dial up and disconnect is with the proxy program.
Where the potential problem would lie, is with the 'Lurk only' or dial-up detection mode and using Task Scheduler to initiate the dial up, where on a connection the proxy (or clients would work the same) will flush whenever there is a conection AND there is anything in the out-buffer OR the in-buffer is below the max buff-in setting.
For instance, my proxy has a new client connection every couple of minutes when cracking RC5 and when only tiny blocks are available. If I was using lurk only, and set to disconnect on 5 minutes of inactivity, it would flush the new incoming blocks as they arrived. Since this occurs on average every 2 minutes, the 5 minute countdown starts over again, and it would never disconnect.
Obviously some of the workarounds would be to have clients build up prior to flushing. This cuts down on the connection frequency, thus lessening the chances that this scenario would occur.
Obviously you have your proxy and the clients set to work very well together. I was just pointing out the potential that this could happen using task scheduler in combination with a high rate of client connections to the proxy.
The key that I saw in Adul's post was to connect to the Internet only once overnight. I don't think that the proxy can schedule that on it's own, but maybe I am wrong. That forces having to use Task Scheduler.
viz