Phishing Protection: Design Documentation: Difference between revisions

Phishing Protection: Design Documentation (view source)

127 bytes removed , 28 May 2006

m

1

edit

@@ Line 73: / Line 73: @@
 The extension has the following four major components.
-* '''Phishing Warden''': One phishing warden exists for the whole application. It monitors HTTP fetch requests and  determines whether the page requested is problematic. It makes this determination, as we've said, by looking the URL up in either a remote or local blacklist. <br><br> You can imagine in the future having additional wardens for other kinds of problematic content, for example a Spyware Warden, or an Unamerican Activities Content Warden to shelter patriotic US citizens from peacenik communist rhetoric. But I digress...
+* '''Phishing Warden''': One phishing warden exists for the whole application. It monitors HTTP fetch requests and  determines whether the page requested is problematic. It makes this determination, as we've said, by looking the URL up in either a remote or local blacklist. <br><br> You can imagine in the future having additional wardens for other kinds of problematic content, for example a Spyware Warden.
 * '''Controller''': There is one controller per browser window. A controller bound to a browser window is responsible for receiving and interpreting user actions and UI activity ("a new tab opened", etc.) within that window.