![[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 12:39 am (UTC)