Change detection and notification: Difference between revisions

Revision as of 04:37, 21 September 2016

Revision as of 08:27, 10 October 2016

Line 10:

==Architectural approaches==

Change detection and notification services can be categorized by the [[software architecture]] they use. Three principal approaches can be distinguished:

* A local client application with a [[graphical user interface]] polls and tracks changes.

=== Server based ===

* A server polls, tracks changes and sends email notifications with a web browser user interface.

A server polls, tracks changes and logs data, sending alerts in the form of email notifications, [[webhook]]s or RSS. Typically there will also be an associated website which the user can manage their configuration.

* A mobile device connects to a [[cloud server]] and can be notified in real time by the server when a change is detected.

*Some Aservices also have mobile device connectsapplications which connect to a [[cloud server]] and can be notified in real time by the server when a change is detected. Newer web technologies make these applications relatively rare.

Examples include [https://www.changedetection.com ChangeDetection] and [https://ingenum-systems.com/WebMonitor WebMonitor].

==== Advantages ====

* No software to install or update.

* No hardware to maintain.

* Accessible from any device where the user can log in to the website.

=== Application based ===

* A local client application with a [[graphical user interface]] polls and tracks changes.

==== Advantages ====

* Cheaper, as all the hosting and bandwidth is provided by the user.

* All data is held by the user.

==Considerations==