what is the best design for a http blocker app?
the requirement is to rediredct certain url's and interact with the user's desktop showing the user a message when a URL is blocked. The memory footprint on the client should be minimal.
I have this model in mind..
3 main components:
1. LSP/WFP driver (3rd party component) - which includes proxy to redirect and show appropriate message in browser
2. Windows Service to manage provide driver with URLs and receive messages from Driver
3. User Mode App (WFP) to a) receive triggers to show blocking/warning notification to user and b) view other related info
1. Load the driver with a list of URLs to be blocked from a windows service
2. When blocking, the driver signals an event to windows service which in turn signals a user mode application (WPF) to show the block and/or warning message.
1. Is there a better way/architecture I'm just not thinking of?
2. I am concerned about terminal servers and citrix servers. How can I implement the tray icon/user desktop interaction in the best and least memory hogging way?
3. The last one concerns the Installation. What installer do you recommend I use. I have used the standard VS installer to this stage but feel I may need more flexibility for this project. Would nullsoft be a good choice? (the 3rd party LSP/WFP driver has it's own installation routine)