![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
wolfwings...managed to port that source code from earlier to a Windows Service that behaves correctly, though it only supports Start/Stop, I couldn't think of a sane state to handle Pause/Resume since there's no solid answer to 'should a web server finish existing requests, close existing requests, or just 'hang' existing requests when paused?' that I could find.
Still, pleased with myself, now to work on a DNS filter that'll automatically integrate itself into the existing network stack, and then integrate that with the main program so it'll be a single executable/service to deal with. Then comes the hard part: Adding configuration screens to adding new domain-names to block like this.
I think there might actually be a market for this sort of thing, if I can manage to make it not break corporate Windows networking's wierd DNS requirements and what-not.
Still, pleased with myself, now to work on a DNS filter that'll automatically integrate itself into the existing network stack, and then integrate that with the main program so it'll be a single executable/service to deal with. Then comes the hard part: Adding configuration screens to adding new domain-names to block like this.
I think there might actually be a market for this sort of thing, if I can manage to make it not break corporate Windows networking's wierd DNS requirements and what-not.
(no subject)
Date: 2008-05-06 10:53 am (UTC)Temporarily stop accepting new requests, returning "temporary condition, please try again in a few moments" results if possible
Finish servicing existing requests
The general idea is "if you need to stop/restart the database, it makes sense to perform an orderly reduction of load without causing large amounts of errors and thus calls to the help desk."
If the administrator wants the existing connections to be closed forcefully, the administrator will stop the service.
As you've noticed, pause/resume semantics are optional.