We would also need an engine to store the personal preferences of users who use the framework to monitor web pages.
In its simplest form, this engine would store the username and password for a user (assuming we wanted to implement this simple type of security rather than some more sophisticated methods), the set of URLs which that person is monitoring, and the frequency with which they would like that HTML page to be differenced against the baseline.
Other preferences stored by the engine would include things like a) should the user be emailed the difference? b) when the difference is done, is the current version made the new baseline? c) what does the user consider to be an "interesting" change to a web page? This would presumably be a list of choices given the functionality that we build into the framework.
We would also need to consider how these personal preferences will be stored. In flat files? In MySQL?
What else needs to be considered here?
From this and the HTML document retrieval and storage design, we have the ability to create a user, store their preferences, and retrieve and store HTML documents based on these preferences.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We would also need an engine to store the personal preferences of users who use the framework to monitor web pages.
In its simplest form, this engine would store the username and password for a user (assuming we wanted to implement this simple type of security rather than some more sophisticated methods), the set of URLs which that person is monitoring, and the frequency with which they would like that HTML page to be differenced against the baseline.
Other preferences stored by the engine would include things like a) should the user be emailed the difference? b) when the difference is done, is the current version made the new baseline? c) what does the user consider to be an "interesting" change to a web page? This would presumably be a list of choices given the functionality that we build into the framework.
We would also need to consider how these personal preferences will be stored. In flat files? In MySQL?
What else needs to be considered here?
From this and the HTML document retrieval and storage design, we have the ability to create a user, store their preferences, and retrieve and store HTML documents based on these preferences.